Prospective agenda for VOQL session in Madrid

[Francois Ochsenbein]

>I will take the liberty to answer
>
>> This sounds quite good for most of the problematic column names.
>>
>> There is however, not a small number of columns (>1800) in the literature
>> with brackets in their names, eg, metal aboundances, forbidden or
>> semiforbidden transitions, etc. How are those cases supposed to be handled?
>>
>
>It has been always agreed that services publishing data are responsible to
>be complaint with the protocols. Services providing access to catalogs
>with columns names including brackets and other funny characters will have
>to either change their names ( ;-) ) or hide with mapping procedures their
>original name.
>
>> The same question arises with table/column names differing just by
>> their case (lower/uppercase names) which should clearly be stated.
>
>to me this case is clear ... SQL is case insensitive. To my knowledge
>only mySQL working with linux make distinctions between upper and lower
>case which I consider a "bug".
>

===> Add Sybase there... 
     And as far as I know, the SQL92 standard asks to use quoted
     table/attribute names containing special characters, or
     for which the distinction lower/upper case is necessary,
     or for names being indentical to SQL syntax keywords.
     Wrriting something like
     select * from "table 3" where "[Fe/H]" < 0
     is a correct statement (in SQL92).
     
--Francois
================================================================================
Francois Ochsenbein       ------       Observatoire Astronomique de Strasbourg
   11, rue de l'Universite F-67000 STRASBOURG       Phone: +33-(0)390 24 24 29
Email: francois at astro.u-strasbg.fr   (France)         Fax: +33-(0)390 24 24 32
================================================================================