> > > > > I would suggest to > > > > > > - make it possible to use the example applications with > > > any dbms for the beginners. Have a README explaining what > > > to do, have an ISO SQL file with 'create table' and > > > 'insert into ...' statement. Just avoid prorietary extensions, > > > use SQL types from standard, that is all you would need. > > Would agree to have an ISO SQL file. > > But on the other hand a example with only an iso sql file > will not run > > out of the box. You must adapt it to your dbms. > > Yes, but it is easier to adapt a ISO file to your dbms than a > file for a dbms you do not know. I would not even consider to > have a look at an example application that seems to be just > for an embedded preconfigured database. > > And I agreed to provide also a hsqldb version as a default version. Agree! So we have both - the iso file and a run out of the box solution. If we use hsqldb as default building the iso file is simple. hsqldb stores all meta data as sql statements! The only thing we must do to support hsqldb and a out of the box example is to integrate the needed jar file in the lib dir.
> > > Therefore the suggestion is to put in an hsqldb setup - > with something > > like an iso file in it. > > > Let us better have a common way to support several dbms: > > - One ISO file that can be used when you have a new dbms > - for several dbms adapted setups, hsqldb being one of it > (maybe the default) > > Why not one subdirectory for each dbms: > > /webapp/WEB-INF/db_iso/README /webapp/WEB-INF/db_iso/create_tables.sql > /webapp/WEB-INF/db_iso/insert_stmts.sql > /webapp/WEB-INF/db_hsqldb/.. > /webapp/WEB-INF/db_mysql/README > /webapp/WEB-INF/db_mysql/databasedump.sql > /webapp/WEB-INF/db_oracle/... > /webapp/WEB-INF/db_postgres/... > /webapp/WEB-INF/README <-- containing infos how to switch db... > > Each of the subdirectories migh contain dbms specific > information. Those who setup a new example application simply > _must_ provide the iso version and might create a version for > arbitrary other dbms (hsqldb prefered). Others then might > easily contribute setups for other databases. Good idea! > > > Any idea what to do with special properties like > autofields? You can > > not use the dbforms autoinc feature in an iso file, each > dbms handles > > the autoinc stuff different= Trigger syntax is different > I would recommend not to use these features within an example > application. It is not surprising to see an example > application work with a preconfigured database, the > surprising thing is when it runs with the dbms you have > there. Btw. isn't there still the NPE after inserting a new > row with autoinc? If this feature is really needed, class > UniqueIDGenerator might be sufficient > for a simple example application. I have a dbms here that > does not support autoInc keys, but I would be curious to see > the examples > run with my system..... Do you have an example how to use UniqueIDGenerator? Regards, Henner ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
