#288 Generate error if a column is ambiguously defined for Oracle

closed
Fred Toussi
engine (144)
1
2013-01-14
2013-01-14
Anonymous
No

Generate error if a column is ambiguously defined for Oracle.

For example if I have 2 tables

CREATE TABLE A
(
ID NUMERIC
MOD_USER VARCHAR(50) CONSTRAINT NN_FW_DSPTCHFRM_MDSER NOT NULL,
MOD_PROGRAM VARCHAR(50) CONSTRAINT NN_FW_DSPTCHFRM_MDPRGRAM NOT NULL,
MOD_DATE TIMESTAMP CONSTRAINT NN_FW_DSPTCHFRM_MDDATE NOT NULL,
);

CREATE TABLE B
(
ID NUMERIC
MOD_USER VARCHAR(50) CONSTRAINT NN_FW_DSPTCHFRM_MDSER NOT NULL,
MOD_PROGRAM VARCHAR(50) CONSTRAINT NN_FW_DSPTCHFRM_MDPRGRAM NOT NULL,
MOD_DATE TIMESTAMP CONSTRAINT NN_FW_DSPTCHFRM_MDDATE NOT NULL,
);

And I run this sql

select ID from a join b on a.id = b.id

In oracle I would get this error:

ORA-00918: column ambiguously defined

I'd like to see similar behavior in HSQLDB as we use HSQLDB to run all our unit tests for our prod system which uses Oracle.

Discussion


  • Anonymous
    2013-01-14

    • priority: 5 --> 8
     

  • Anonymous
    2013-01-14

    It would be good if this behavior(throwing exception) was present if sql.syntax_ora=true

     
  • Fred Toussi
    Fred Toussi
    2013-01-14

    • assigned_to: nobody --> fredt
    • priority: 8 --> 1
    • status: open --> closed
     

  • Anonymous
    2013-01-15

    That works great, thanks for the tip!