I was under the impression that the purpose of a "compatibility mode" was
to make the product more compatible and to better support the syntax of a
specific RDBMS. Why would adding this change under the PostgreSQL
compatibility mode affect MySQL?
-Joe
--
You received this message because you
> Ah, I guess the main problem is the "()" at the end. I didn't see that
> first, sorry.
>
> Could you change the query to:
>
> SELECT getNextIdAndUpdate() AS getNextIdAndUpdate
I certainly could, but my goal was to change nothing in the code to
accommodate my unit testing. Referencing the colum
I am trying to create a simple btree index in postgreSQL mode with the
USING BTREE syntax. The statement is failing. This will recreate the
exception:
CREATE TABLE table_name (my_column INTEGER);
CREATE INDEX table_idx_00 ON table_name USING BTREE (my_column);
Is this syntax not supported?
--
Thomas,
There is no error message. I thought I worded the question quite
well. I will summarize as best I can.
Java code that I do not wish to change is calling a stored function in
H2 in PostgreSQL mode. Java is pulling the value by name instead of
by index.
My question is, is there any way
Correction to my above column name. The column name includes the
function parenthesis:
PUBLIC.GETNEXTIDANDUPDATE()
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to h2-database@googlegroups.com.
To unsubs
I am using H2 in embedded mode to unit test some DAO classes. I found
one of the DAOs calls a user-defined function in the PostgreSQL
database. I tried to mock the function by writing a java method under
an alias in H2. I used this simple class for my test:
public class UserDefinedDbFunctions {
