2005 introduces the snapshot isolation level (their name for their MVCC implementation). 2000 and earlier were plagued by deadlock issues. I do not know of an easy way around that besides "protecting" those tests individually via the "skipping" mechanism. I do not have the time to do that right now. And honestly, I don't care about SQLServer pre-2005... So if you can run against 2005, great, lets do that; if not, lets just leave this one be for now.
jTDS (at least when I last tried) will not work with SQLServer 2005 for a couple of reasons (for example, jTDS bombs when you try to set 4096 as the isolation level). It has been about a year now, so this may have changed. -----Original Message----- From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 05, 2006 2:50 PM To: Steve Ebersole Cc: hibernate-dev@lists.jboss.org Subject: Re: [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors] jtds guys say their driver is recommended for hibernate ;) Only this one hangs. It's not a problem to use the MS jdbc driver but is it necessary to run on 2005. We now have only 2000. Steve Ebersole wrote: >Yes, you should use the MySQL5Dialect... > >For SQLServer you must: >1) use 2005 and the correspnding MS driver (no jTDS!) >2) use the snapshot isolation level (hibernate.connection.isolation >4096) >Otherwise, yes that (and others, I believe) will hang. > >Here are my local settings for SQLServer (2005 Express): >hibernate.dialect org.hibernate.dialect.SQLServerDialect >hibernate.connection.url jdbc:sqlserver://localhost:1681 >hibernate.connection.driver_class >com.microsoft.sqlserver.jdbc.SQLServerDriver >hibernate.connection.isolation 4096 >hibernate.connection.username hibernate >hibernate.connection.password hibernate > > > >-----Original Message----- >From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >Sent: Tuesday, December 05, 2006 2:04 PM >To: Steve Ebersole; hibernate-dev@lists.jboss.org >Subject: Re: [Fwd: hibernate-mysql50-testsuite Build Completed With >Testsuite Errors] > >Yes. The tests run with the innodb dialect. Prabhat mentioned that there >is a separate dialect for mysql5. Should I set it for tests on mysql >5.0? > >There is a problem with the SQL server tests. EJB3LockTest freezes >things until build timeout comes. Is it possible to set per test >timeouts so a single test cannot break the whole build? Or say if any >test/testcase takes longer than a minute then fail it and continue? > >EJB3LockTest should be disabled or repaired so I can enable regular >SQLserver tests. > >Thanks. > >Steve Ebersole wrote: > > > >>Another question. Did you create this with InnoDB as the default >>engine? If not, please do so. Running with MyISAM is not an accurate >>representation of a valid production environment. >> >>Thanks. >> >>-----Original Message----- >>From: Aleksandar Kostadinov [mailto:[EMAIL PROTECTED] >>Sent: Sunday, December 03, 2006 6:18 AM >>To: hibernate-dev@lists.jboss.org; Steve Ebersole >>Subject: [Fwd: hibernate-mysql50-testsuite Build Completed With >>Testsuite Errors] >> >>As failings with mysql 5.0.27 are similar to these of 4.1.22 I consider >>results are consistent. >> >>Please contact me if you don't agree. >> >> >> >> _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
