Actually, it turns out that it is not that HsqlDB does not support transactions, looks like the Hsqldb-1.7.0 JDBC driver does not support the setTransactionIsolation() function. Plus, it looks like the "LOCK TABLE" syntax used in TableIdGenerator is proprietary for MySQL.
So, I guess, the real question is how to lock HsqlDB in an elegant fashion, without adding yet another function for Hsqldb in IdGenerator? ----- Original Message ----- From: "Sasvata (Shash) Chatterjee" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 16, 2002 9:18 PM Subject: IdGenerator change > Hi! > > We are trying to use HsqlDB with Excalibur-Datasource's IdGenerator. The > problem I ran into was that looks like TableIdGenerator assumes that the > backend DB is transaction capable, unless it is MySQL. I wanted to change > AbstractDataSourceIdGenerator.configure to use a configuration item > "use-transaction" to allow a more generic way of specifying this, instead of > setting/using m_dbType for MySQL/not-MySQL. > > Are there any problems with this approach? > > Thanks, > Shash > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
