Maybe we shouldn't bother to quote schemas, assuming that it's the duty of client?
Unfortunately after reading ODBC docs I have no idea, but there's no hints that the result will be quoted. Regards, -- Ilya Kasnacheev пт, 7 сент. 2018 г. в 15:38, Igor Sapego <[email protected]>: > Well, ODBC applies quotes to all schemas. It makes sense to > check and not apply quotes to PUBLIC, but this won't help in > all other cases, when cache-name-schema is used. > > Best Regards, > Igor > > > On Fri, Sep 7, 2018 at 2:13 PM Ilya Kasnacheev <[email protected]> > wrote: > >> Hello! >> >> It's actually very strange that we have quotes around PUBLIC since it's >> supposed to be used quote-free. I will take a look. >> >> Regards, >> >> -- >> Ilya Kasnacheev >> >> >> пт, 7 сент. 2018 г. в 14:07, Igor Sapego <[email protected]>: >> >>> It happens, because ODBC returns schema name in quotes, >>> so seems like QLIK adds its own quotes around it, as it encounters >>> non standard characters (quotes). >>> >>> I think, it is a QLIK's error, as our ODBC driver explicitly states, >>> that no >>> additional quotes should be used around identifiers. And even if it >>> choose >>> to apply quotes to "PUBLIC" result obviously should not be a ""PUBLIC"". >>> >>> Best Regards, >>> Igor >>> >>> >>> On Thu, Sep 6, 2018 at 6:43 PM limabean <[email protected]> wrote: >>> >>>> Although I specify lower case public in the odbc definition in Windows >>>> 10, >>>> the QLIK BI application, on its ODBC connection page, forces an upper >>>> case >>>> "PUBLIC" as you can see in the screen shot, and as far as I can tell >>>> there >>>> are no options to change that. >>>> >>>> QlikOdbcPanel.png >>>> < >>>> http://apache-ignite-users.70518.x6.nabble.com/file/t361/QlikOdbcPanel.png> >>>> >>>> >>>> >>>> >>>> -- >>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >>>> >>>
