Hi, there might be a misunderstanding here of how Ignite SQL grid is
implemented. Please note that Ignite does not use H2 as a storage. Ignite
uses H2 only as a parser and planner. H2 hands a parsed and planned
statement over to Ignite and then Ignite maps the statement to
get/put/create cache/etc.
Hello, Alexey.
Thank you for clarification.
Is there any way to use in Ignite tables created directly in H2?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Ignite's PRIMARY KEY does not map to H2 PRIMARY KEY constraint so you not
seeing a primary key in H2 is OK.
Ignite's PRIMARY KEY designates a binary object that Ignite SQL Grid will
create for the underlying data grid cache key. Thus, in your example you
will end up with two binary objects stored
Hi,
Suppose we have following DDL:
CREATE TABLE TEST
(
org_id INT NOT NULL,
drug_id INT NOT NULL,
price DOUBLE NULL,
qtty INT NULL,
inter_id INT NULL,
trade_id INT NULL,
med_id INT NULL,
medp_id INT NULL,
avgprc DOUBLE NULL,
avgprc_region DOUBLE NULL,
region_id INTEGER NULL,
