Nice to hear.
Please, keep us updated about what QLIK thinks about the issue.
Thank you in advance
Best Regards,
Igor
On Mon, Sep 10, 2018 at 10:50 PM limabean wrote:
> Thank you very much for the thorough discussion/explanation and pending fix
> for public schemas. Much appreciated !
>
>
Thank you very much for the thorough discussion/explanation and pending fix
for public schemas. Much appreciated !
As an aside, I also contacted QLIK to see if they will fix their product
behavior, which does not seem correct to me either.
--
Sent from:
I've filed a ticket: [1]
[1] - https://issues.apache.org/jira/browse/IGNITE-9515
Best Regards,
Igor
On Mon, Sep 10, 2018 at 2:56 PM Ilya Kasnacheev
wrote:
> Hello!
>
> Yes, I'm pretty confident that PUBLIC should work without quotes. I'm even
> not sure that it would work even with ordinary
Hello!
Yes, I'm pretty confident that PUBLIC should work without quotes. I'm even
not sure that it would work even with ordinary double quotes set.
Regards,
--
Ilya Kasnacheev
пн, 10 сент. 2018 г. в 14:28, Igor Sapego :
> Ilya,
>
> If we won't bother with quotes, then many other tools will
Ilya,
If we won't bother with quotes, then many other tools will stop working,
as cache-names-schemas MUST be quoted, but they won't be. By the way,
even QLIK will not work with any other schema, except for PUBLIC.
So for now, what I propose is not apply quotes to PUBLIC schema. This is
the only
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 :
> Well, ODBC applies quotes to
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
wrote:
> Hello!
>
> It's actually very strange that we
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 :
> It happens, because ODBC returns schema name in quotes,
> so seems like QLIK adds its
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
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
Hi,
Here is my ODBC specification.
The schema is specified as Public and this looks (identical?) like the
example in the documentation:
On Thu, Sep 6, 2018 at 11:06 AM Вячеслав Коптилин
wrote:
> Hi,
>
> > I have tried various things on the Java side to make the Public schema
> explicit, such
Hello!
Please try using public (lower case) as schema, since quotes force case
sensitivity.
Regards,
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 18:25, David Robinson :
> I have no control over the format of the query coming through the ODBC
> driver.
>
> That is done automatically as far as I
I have no control over the format of the query coming through the ODBC
driver.
That is done automatically as far as I know by the[QLIK BI tool that is
leveraging the ODBC driver
to try to read data.
Are you suggesting it is QLIK adding the extra quotes that is causing the
problem with the H2
Hello!
SELECT COUNT(*) FROM ""PUBLIC"".CITY <-- I don't think you need any quotes
around PUBLIC.
Regards,
Ilya.
--
Ilya Kasnacheev
чт, 6 сент. 2018 г. в 16:59, limabean :
> Scenario:
> 64-bit ODBC driver cannot read data created from the Java Thin driver.
>
> Ignite 2.6.
> Running a single
Hi,
> I have tried various things on the Java side to make the Public schema
explicit, such as this:
If I'm not mistaken the schema can be specified as a parameter of ODBC
connection string.
Please take a look at this page:
Scenario:
64-bit ODBC driver cannot read data created from the Java Thin driver.
Ignite 2.6.
Running a single node server on Centos to test this.
First:
Using Intellij to remotely run the sample code from the Ignite Getting
started page here on SQL:
First Ignite SQL Application
16 matches
Mail list logo
