google-code-export / h2database

Automatically exported from code.google.com/p/h2database
0 stars 1 forks source link

USING INDEX clause is not provided #263

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
We are using a Oracle 10g R2 database.
For unit tests we'd like to use a InMemory database, maybe H2.
We started with HSQLDB and converted in our creating table scripts Oracle's 
NUMBER to INTEGER, VARCHAR2 to VARCHAR etc.

But now we are at a point where we stuck:
We have a lot of USING INDEX statements in our scripts and did not find any 
equivalent in HSQLDB or H2.

We only found on the roadmap:
MySQL compatibility: DELETE .. FROM .. USING - See 
http://dev.mysql.com/doc/refman/5.0/en/delete.html 

But this is not what we need. One example, what we have (after the above 
mentioned replacements):
----------------------------
CREATE TABLE EQUIPMENT_MST_PP
(
  RAWID             INTEGER               NOT NULL,
  MODEL_NAME        VARCHAR(30)           NOT NULL,
  APPLICATION_NAME  VARCHAR(30),
  EQP_ID            VARCHAR(30)           NOT NULL,
  CREATE_DTTS       TIMESTAMP(6),
  CREATE_BY         VARCHAR(30),
  LAST_UPDATE_DTTS  TIMESTAMP(6),
  LAST_UPDATE_BY    VARCHAR(30),
  CONSTRAINT IDX_EQUIPMENT_MST_PK
 PRIMARY KEY (RAWID) USING INDEX TABLESPACE EES_MST_IDX
)
TABLESPACE EES_MST_DAT
;
----------------------------

So our question is:
Is there a plan to support this Oracle compatibility?
If yes, when will it be possible to use such a feature?
We hope, we can get an answer until Christmas :-)

Thank you for your support!

Original issue reported on code.google.com by andym...@gmx.de on 10 Dec 2010 at 1:23

GoogleCodeExporter commented 9 years ago
I'm sorry, I don't plan to support TABLESPACE, because it's not a popular 
feature request so far. If many people do like to support it, this will change 
of course, but currently not.

But patches are always welcome of course!

Original comment by thomas.t...@gmail.com on 12 Dec 2010 at 12:14

GoogleCodeExporter commented 9 years ago
OK, we understand, it is (sadly) not popular enough. 
Thanks for the quick reaction on this issue.
If we find enough time, we'll try to create a patch.

Original comment by andym...@gmx.de on 13 Dec 2010 at 3:11