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
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
I can - but apparently not with a separate process that gets notifications
- which is the design point I was seeking.
Thanks again.
On Wed, Jun 1, 2016 at 12:55 PM, Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> You can easily implement such a thing as a part of transaction logic.
>
With Ignite 1.5.0:
I have two caches.
Cache 1 stores a Person object like this:
personCache.put(id, PersonObj1);
The Person class has only a single field in it declared like this:
@QuerySqlField(index = true)
private int personId;
Cache 2 stores a Person Attribute object like this:
