We have just updated our H2 implementation from version .061 to .104. It would appear that column aliasing in a SELECT statement on any table has been broken (but still works OK on query literals).
For the following SQL: SELECT "DummyCol" as "Foo", 'literal' as "Bar" FROM "DummyTable" we would expect to see a resultSet with two columns, Foo and Bar. In . 061 this was the result, however on .104, we get a resultSet with two columns named "DummyCol" and "Bar" which completely invalidates our interface. Is anyone else experiencing this with .104? It seems a very fundamental problem! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
