Further testing shows that when 'SET EXCLUSIVE 1' is NOT executed first, the statement runs normally.
On Tuesday, September 9, 2014 1:23:30 PM UTC-4, D. Aldenderfer wrote: > > When our application starts it performs schema updates to the H2 database > as needed. > > Before performing updates we "SET EXCLUSIVE 1" and make sure that no > table locks exists ( "SELECT COUNT(*) FROM information_schema.locks" ). > > The following schema update statement hangs the application: > > alter table ENCODED_ITEM add column if not exists TEXT_ENCODED_ITEM clob > > Other "alter table add column" statements where the type is not clob do > not display this behaviour? > > We are using version 1.4.181 > > Any ideas? > > > -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
