On 2016-01-07 07:13 AM, Tim wrote:
I have looked at the code and found the issue. I am using the PG Server for
connectivity and it has the PostgreSQL mode
hard coded which overrode the MODE I set when starting H2. I am logging into
the PG Server with an admin user to
generate the pg_catalog after start up.
That sounds a little hacky. The PG driver internally generates queries which require H2 to be in PG mode. I don't think
mixing and matching modes is going to work very well.
I have also found some other issues in with the pg server:
* If DATABASE_TO_UPPER=false the pg_catalog is created on each connection as
conn.getMetaData().getTables(null,
"PG_CATALOG", "PG_VERSION", null); is case sensitive.
* The pg_catalog script should drop the regproc domain if it exists.
* The row descriptions are in lowercase StringUtils.toLowerEnglish(names[i]),
not sure if that is a postgres thing but
it should be actual case or have an option to be the correct case.
If have also added a few things to make it improve the compatibility with SQL
Server: DATEPART & FORMAT functions plus
constants so the functions can be used interchangeably, i.e. yy, qq, mm, etc.
Have to submit a patch/issue or more info if you are interested.
Patches for this stuff, however, would be most welcome :-)
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
