Hello! CREATE TABLE will create table in PUBLIC schema. Hence the conflict.
Regards, -- Ilya Kasnacheev пн, 14 окт. 2019 г. в 22:59, Stephen <[email protected]>: > I'm seeing the same thing in Visor. However, I'm not seeing the behavior I > would expect. For instance (using sqlline) > > create table batch_test (x varchar(10), y int, z float, PRIMARY KEY (y)) > with "CACHE_NAME=foo"; > insert into "foo".batch_test (x, y, z) VALUES ('FOO', 6, 5.1); > > *Error: Failed to parse query. Schema "foo" not found; SQL statement:* > > Typing - > > insert into batch_test (x, y, z) VALUES ('FOO', 6, 5.1); > > does insert the values. With a cache being essentially equal to a schema, I > would expect to be able to have the same table name in different caches. > The > clearest example of this unexpected behavior is the following > > 0: jdbc:ignite:thin://127.0.0.1:10800> create table batch_test (x > varchar(10), y int, z float, PRIMARY KEY (y)) with "CACHE_NAME=foo"; > No rows affected (0.039 seconds) > > 0: jdbc:ignite:thin://127.0.0.1:10800> create table batch_test (x > varchar(10), y int, z float, PRIMARY KEY (y)) with "CACHE_NAME=bar"; > > *Error: Table already exists: BATCH_TEST (state=42000,code=3007)* > > I can only create > foo.batch_test > > I'm unable to create bar.batch_test if foo.batch_test already exists. The > behavior I would expect is that both of these succeed. If I'm not > understanding the data model here, can you clarify? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
