In my attempts to use a different database than H2, one of the issues I faced was the initial data. Through the DataSourcePopulator we directly execute SQL queries which causes troubles like - the exception "table \".*\" not found.*\n*.*" works for H2 and MySQL, PostgreSQL returns "ERROR: relation "widget" does not exist". - set @variable is not the correct syntax for PostgreSQL - a boolean value must be TRUE or FALSE (instead of 'Y' and 'N') to work with both H2, MySQL and PostgreSQL - and last but not least: a change in sequence strategy means that the queries won't be executed because of "next value for user_id_seq".
Some of the initial data is actually essential to let the portal work. If you create a new account but don't have a filled page_layout table, the user can log in but immediately gets a stacktrace. I want to propose to create a new populator that uses JPA to create the objects instead of native sql queries. Jasha Joachimsthal Europe - Amsterdam - Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522 4466 US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414 4776 (toll free) www.onehippo.com
