IVOA Support Interfaces 1.1

[Kristin Riebe]

Hi grid,

right, now I think I have a better understanding of the discussion:

I thought we were talking about having something like
.../tables/database/schema/table
(thinking of SQL-Server, which has the schema in between).
That's why I did not want to have the schema there.

But if we have instead
.../tables/schema/table
were "schema" corresponds to "database" in MySQL, then I'd like to keep 
it or at least add a possibility to filter by it.
We have a service with multiple MySQL-databases (schemas), and many 
tables for each of them. So I would want to have the possibility to just 
list the schemas (without all the tables) and also filter by schema 
(listing tables for just one schema).

Cheers,

Kristin



Am 19.06.2015 um 10:05 schrieb Marco Molinaro:
> Hi grid,
>
> One clarification on the MySQL schemas. Actually MySQL calls database
> what usually is referred to as a schema.
> So, as far as qualified table names are ok, I think MySQL will not
> have a problem with neither solution.
>
> Then, I have no specific preference on the choice. I thought I'd
> prefer 1, but I'm not sure.
> I think that the change in the /tables endpoint comes out of TAP
> revision mainly, and probably is related to whether we want to expose
> actual tablesets or structured tables inside some hierarchy.
> My feeling is that the use cases are more for tables collected, less
> for how they are organized in catalog.schema.* solutions.
>
> So, if we think the model is flawed, probably it's better to fix it.
> However this means asking providers to change their XML outputs...and
> that is a major thing...that's why I'm probably ok whatever the
> majority of involved parties choose.
>
> Cheers,
>      Marco
>
>
> 2015-06-18 17:35 GMT+02:00 Kristin Riebe <kriebe at aip.de>:
>> Hi grid,
>>
>> I vote for version 1, since MySQL doesn't have a schema and we are using
>> MySQL databases. So I would need to come up with something arbitrary
>> (default?) for the schema that does not have any useful meaning for us. If
>> this introduces inconsistencies with that XML model, then I vote for fixing
>> that model as soon as possible.
>>
>> Cheers,
>>
>> Kristin
>>
>>
>>
>> Am 18.06.2015 um 09:59 schrieb Brian Major:
>>>
>>> Hi grid,
>>>
>>> In support of a more scalable VOSI /tables interface, we will start a
>>> 1.1 WD of the IVOA Support Interface document.
>>>
>>> There is, however, one issue that remains:  whether or not to include
>>> the $dbSchema segment in the rest interface to the new /table endpoint.
>>> An initial email thread of a discussion of this point can be seen here:
>>>
>>> http://mail.ivoa.net/pipermail/grid/2015-May/002728.html
>>>
>>> Should the REST endpoint match the, potentially flawed, XML model which
>>> includes the dbSchema (option 1), or should we try to correct the new
>>> /table REST endpoint now and fix the XML model later? (option 2).  (If
>>> I've misunderstood the arguments please correct me.)
>>>
>>> My preference is for consistency so vote option 2, but I'd like to hear
>>> opinions from the wider grid community so please state your opinions.
>>>
>>> Regards,
>>> Brian
>>>
>>
>> --
>> -----------------------------------------------------------------
>> | Dr. Kristin Riebe
>> | eScience & GAVO
>> |
>> | Email: kriebe at aip.de
>> | Phone: +49 331 7499-377
>> | Room:  B6/25
>> -----------------------------------------------------------------
>> | Leibniz-Institut für Astrophysik Potsdam (AIP)
>> | An der Sternwarte 16, D-14482 Potsdam
>> | Vorstand: Prof. Dr. Matthias Steinmetz
>> |
>> | Stiftungsverzeichnis Brandenburg: 26 742-00/7026
>> -----------------------------------------------------------------
>

-- 
-----------------------------------------------------------------
| Dr. Kristin Riebe
| eScience & GAVO
|
| Email: kriebe at aip.de
| Phone: +49 331 7499-377
| Room:  B6/25
-----------------------------------------------------------------
| Leibniz-Institut für Astrophysik Potsdam (AIP)
| An der Sternwarte 16, D-14482 Potsdam
| Vorstand: Prof. Dr. Matthias Steinmetz 	
|
| Stiftungsverzeichnis Brandenburg: 26 742-00/7026
-----------------------------------------------------------------