Well the problem is that we have a few multi-catalog/schema tests: tests that specifically test referring to objects from multiple catalogs/schemas. And on top of that we have schema export tests that test being able to create catalogs and schemas.
So we have a few options. We can pre-determine all the needed catalogs and schemas and make sure we set those up in the database server ahead of time. But that still leaves problems with the schema-export tests for creating namespaces. That is a feature we need to be able to test. Some databases simply won't be able to support this (Oracle). We could do something similar in terms of allowing a determinate set of catalogs/schemas to be created. A few databases actually allow specifying which catalogs/schemas can be created (by what users); so we could explore that as well. Another option is to define 2 users for Hibernate ORM tests: one with normal privs and one with elevated privs. On Sun, Jul 26, 2015 at 3:11 AM Sanne Grinovero <sa...@hibernate.org> wrote: > On 23 July 2015 at 17:41, Steve Ebersole <st...@hibernate.org> wrote: > > Another change is to make sure our test user has create/drop privileges > on > > all databases, and to be able to create/drop databases: > > > > grant create, drop on *.* to 'hibernate_orm_test'@'localhost'; > > > > We will need similar for the other databases too. > > That limitation was actually intentional. > > I think most users will have Hibernate connect via a > limited-privileged user, so you don't think there would be value in us > actually testing using the more limited privileges? > > I'm ok to change it, but - unless it's too inconvenient to get current > tests reliable - I'd prefer to create a second user for when test > infrastructure code need to create/drop databases. Why are you needing > this? > > -- Sanne > > > > > > > > > On Tue, Jul 21, 2015 at 6:02 PM Sanne Grinovero <sa...@hibernate.org> > wrote: > >> > >> On 20 July 2015 at 17:41, Steve Ebersole <st...@hibernate.org> wrote: > >> > Sanne for MariaDB (and MySQL if we ever add it) we need to add at > least > >> > one > >> > more setting: > >> > > >> > sql-mode="traditional" > >> > >> I've applied this change. > >> > >> --Sanne > >> > >> > > >> > We could probably get away with less ANSI compliant mode, but after > days > >> > playing with this I just want to cover my bases :) > >> > > >> > On Sat, Jul 18, 2015 at 3:37 PM Sanne Grinovero <sa...@hibernate.org> > >> > wrote: > >> >> > >> >> Thanks, great suggestions! > >> >> I've applied these and some more. > >> >> > >> >> The MariaDB configuration: > >> >> - > >> >> > >> >> > https://github.com/hibernate/ci.hibernate.org/blob/master/roles/mariadb-server/files/my.cnf > >> >> > >> >> The PosgreSQL configuration files: > >> >> - > >> >> > >> >> > https://github.com/hibernate/ci.hibernate.org/blob/master/roles/postgres-server/files/pg_hba.conf > >> >> - > >> >> > >> >> > https://github.com/hibernate/ci.hibernate.org/blob/master/roles/postgres-server/files/postgresql.conf > >> >> > >> >> Both are running with these settings now on each CI slave. > >> >> Sanne > >> >> > >> >> On 18 July 2015 at 00:49, Steve Ebersole <st...@hibernate.org> > wrote: > >> >> > [18:45] <sebersole> whoa.. > >> >> > [18:45] <sebersole> sannegrinovero: we definitely need this for > >> >> > mariadb > >> >> > on > >> >> > ci... > >> >> > [18:46] <sebersole> sync_binlog=0 innodb_flush_log_at_trx_commit=0 > >> >> > innodb_doublewrite=0 > >> >> > [18:46] <sebersole> tests were much faster > >> >> > > >> >> > These were suggested to me on the #mariadb list. I added them to > my > >> >> > local > >> >> > /etc/my.cnf file and the tests were significantly faster. > >> >> > _______________________________________________ > >> >> > hibernate-dev mailing list > >> >> > hibernate-dev@lists.jboss.org > >> >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
