Please use the google group to ask questions - thanks.

No. Afraid not.

I wonder what problems you would hit with that. Let me know if/when you hit them.

Thanks, Rob.

The following is my stack trace. I can my mysql configuration to support transactions but when I'm in development mode it's nice to leave it in MyISAM mode:

javax.persistence.PersistenceException: com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException: Can't call rollback when autocommit=true
com.avaje.ebean.server.transaction.JdbcTransaction.rollback(JdbcTransaction.java:483)
com.avaje.ebean.server.transaction.JdbcTransaction.rollback(JdbcTransaction.java:460)
com.avaje.ebean.server.core.QueryRequest.rollbackTransIfRequired(QueryRequest.java:103)
com.avaje.ebean.server.core.DefaultServer.findList(DefaultServer.java:996)
com.avaje.ebean.query.DefaultOrmQuery.findList(DefaultOrmQuery.java:394)
org.avaje.ebean.spi.jpa.EbeanEntityManagerFactory$QueryWraper2.getResultList(EbeanEntityManagerFactory.java:463)

Actually this might be a different problem to what I was thinking... in that it looks like the connections look to be in autocommit=true mode.

That is, it could be that Ebean is assuming that the connection pool by default creates connections with autocommit=false. If Ebean is not checking this that could be considered a bug...

Are you able to check that the DataSource is in fact defaulting autocommit=true... and can you set it to autocommit=false? Perhaps this is actually what you meant but I didn't understand?

Thanks, Rob.