I'm looking for some assistance developing the new opensolaris.org user management web application (http://src.opensolaris.org/source/xref/website/auth/trunk/).
In order to test the application properly as it is developed, we need to have a realistic data corpus. At the moment the test database consists of just 26 users (see http://src.opensolaris.org/source/xref/website/auth/trunk/AuthDB/src/sql/populate_db.sql#90), whereas a more realistic number would be 100,000. I'm looking for some help to generate this data. Rather than explicit import statements it will probably be better to use a data file in conjunction with the Derby bulk data import facilities, see http://db.apache.org/derby/docs/dev/tools/ctoolsimport16245.html At the moment I'm using Derby (http://db.apache.org/derby/) as the underlying database, because it is possible to embed Derby inside Tomcat. This is important during development because it means people can try out the application without having to install and configure a separate database, e.g. Postgres or MySQL. All that is required to run the application is to copy the WAR file into the Tomcat webapps directory, or even easier, just open the project in NetBeans and press F6. However we need to figure out if we can also use Derby in production, or if we need to switch to something else such as Postgres. And for that we need a realistically-sized test database. I'm also wondering if we need a separate website-dev mailing list, or should we just continue using website-discuss? -- Alan Burlison -- _______________________________________________ website-discuss mailing list [email protected]
