ADQL using reserved words in tables

[ada nebot]

Hi Gregory, 

Yes I have tried the ASCII double quotes (my email converted those into funny characters).  
It doesn’t work - at least not from TOPCAT. 

Cheers,
Ada

> On 14 Nov 2019, at 09:56, Gregory MANTELET <gregory.mantelet at astro.unistra.fr> wrote:
> 
> Hi Ada,
> 
> Indeed `public` is a reserved keyword and it should not be allowed to write it as such. You need to use double quotes.
> I see in yours queries that you used funny double quote characters.....have you tried the normal ASCII ones?
> The query would look like this:
> 
> SELECT TOP 10 * FROM "public".hipparcos_newreduction
> Cheers,
> Grégory
> 
> 
> On 14/11/2019 09:17, ada nebot wrote:
>> Hi, 
>> 
>> While performing a tutorial in a VO School we have seen that access through TAP using ADQL 
>> on tables/catalogues containing the reserved word public on them was not possible. 
>> We tried as stated in the documentation using double quotes around the word and lots of different combinations.  
>> But that did not solve the issue. Has anyone a clue on how to do this? 
>> 
>> Thanks,
>> Ada
>> 
>> Here are the queries we tried: 
>> 
>> SELECT TOP 10 * FROM public.hipparcos_newreduction
>> 
>> SELECT TOP 10 * FROM “public”.hipparcos_newreduction
>> 
>> SELECT TOP 10 * FROM “public.hipparcos_newreduction”
>> 
>> SELECT TOP 10 * FROM  'public’.hipparcos_newreduction
>> …
>> SELECT TOP 10 * FROM  ''public''.hipparcos_newreduction
>> and even something like 
>> 
>> SELECT TOP 10 * FROM  \’public\’.hipparcos_newreduction
>> …
>> 
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dal/attachments/20191114/b8f8af5f/attachment.html>