Hi, thanks for the fix. It caused one regression though (at least from my point of view):
When retrieving the index information, the automatically generated index for the primary key is no longer marked as a "primary key" index. Which in my case means that I re-create the correct SQL for the PK constraint but I also build an additional CREATE UNIQUE INDEX statement which is incorrect. Cheers Thomas On 30 Dez. 2008, 14:55, "Thomas Mueller" <[email protected]> wrote: > In the next release, the column PK_NAME of > DatabaseMetaData.getPrimaryKeys will contain the constraint name > instead of the index name. > > Regards, > Thomas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
