Lev wrote: > from the previous emails, i understand that i can employ > the import.sql approach to create a database and can drop > a database by executing SQL commands. > > however, it seems to be a limitation not to be able to > do all of this programatically in the essence of the > hibernate SchemaExport() example that i provided > earlier. > There is no limitation that I can see.
The reason one drops a table is because its table structure has changed. And if its structure has changed and you are using JPA annotations then you need to recompile your changed classes anyways and restart your application - which coupled with the "update" or "create" hibernate option recreates your table as per your compiled classes on restart. If the table structure has not changed then use "delete from <sometable>" to clear out the data. What's the issue / limitation? Are you dynamically constructing classes or something? --Nikolaos > does anybody have any other ideas on the drop/create > can be accomplished programatically all in the same > application deployment? > > thanks, > lev > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Stripes-users mailing list > Stripes-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/stripes-users > > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
