When I set the DATABASE_TO_UPPER property set to false Table- and FieldNames are 'stored-as-is', so when I execute 'CREATE TABLE Customers ...' and retrieve the metaData I get 'Customers'. That's what I want and that's what I need.
But what I don't want is to ACCESS the table in a case-sensitive way. When I execute two queries: SELECT * from Customers and SELECT * from CUSTOMERS I expect both to return the same results because the SQL standard says that sql statements should be interpreted in a case-insensitive way. With the DATABASE_TO_UPPER set to false I even can execute: CREATE TABLE customers and CREATE TABLE Customers ending up with two different tables where the SQL Standard requires the second to throw a 'Table already exists' exception. The changelog says: "DATABASE_TO_UPPER: when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL" But it's not compatible with MySQL at all (and I doubt it is with PostgreSql) Sije de Haan -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
