1) I would guess that this because of temp tables. Hibernate allows the Dialect to say whether or not the database supports DDL statements within a transaction. Sybase does not override this; the default is to query the JDBC metadata to see whether DDL is allowed within transactions (see links below). My guess is that Sybase simply does not report this accurately based on whether this option you mention is set or not set; it probably just blindly says "yeah, we support it...". We can look at changing this behavior for Sybase. You can imagine where this goes on the priority list ;) 2) Believe it or not, as the lead of Hibernate I actually do subscribe to the hibernate-dev list ;)
http://java.sun.com/j2se/1.4.2/docs/api/java/sql/DatabaseMetaData.html#dataDefinitionCausesTransactionCommit() http://java.sun.com/j2se/1.4.2/docs/api/java/sql/DatabaseMetaData.html#dataDefinitionIgnoredInTransactions() On Fri, 2007-05-25 at 14:39 +0300, Aleksandar Kostadinov wrote: > Looking at the latest hibernate cruisecontrol builds I see around 20 > sybase tests are passing because I've enabled "ddl in tran" option of > tempdb database. > It is not recommended by sybase to use DDL in transactions so I think it > should be good to avoid it in future hibernate releases if possible. > > Regadrs, > Aleksandar _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev