Hi, This sounds like a bug to me. Unfortunately, I don't have a workaround that works for both H2 and PostgreSQL. What does work is:
create sequence "test_id"; select "test_id".nextval; Regards, Thomas On Monday, December 26, 2011, Eduardo Velasques wrote: > Hi! > > I've extends compatibility in my apps with PostgreSQL to support H2 too. > > I used quotes in all names of tables, fields and sequences to prevent > reserved keywords: > > http://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.0#Reserved_words > > But with H2 I detect an important issue and this don't works with > sequences. > > If create a sequence like this (with quotes name): > > create sequence if not exists "test_id" starts with 1; > > This never will works: > > select nexval('test_id') > > Because nextval automaticaly convert to uppercase and the "test_id" is > created into the DB with lowercase. > > Have some workaround? > > Thank you. > > -- > Eduardo Velasques > > -- > 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]<javascript:_e({}, 'cvml', > '[email protected]');> > . > To unsubscribe from this group, send email to > [email protected] <javascript:_e({}, 'cvml', > 'h2-database%[email protected]');>. > For more options, visit this group at > http://groups.google.com/group/h2-database?hl=en. > -- 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.
