Hi all,

If I wanted to split my import.sql into multiple files and still have that run on startup, how would I go about doing that? My import.sql is getting a little large and I was hoping I could maybe leave it in the same place and have one for each jar file that provides some functionality my web app is using. Alternatively, if it grows really large, I'd like to be able to specify a list of files to scan.

I am using JBoss Seam for my application framework.


Thanks,
Walter

you can do this with @<path>\b.sql at the end of import.sql file.

Let we have import.sql,a.sql and b.sql

write like this

import.sql
...
..
@\mysql\a.sql


a.sql:
...
..
@\mysql\b.sql

Christian,

That is perfect - there is a little bit of work I have to do, but so far it looks promising. The other suggestion is valid if I'm running it through MySQL Query Browser or command line probably, but for this task, it won't work.

The solution that I'm implementing is finding all occurrences of database.configuration through getResources( ... ). Then for the entries that are in an archive, I have to use Java's support for reading Zip files. Once I locate all the files and read all the content, I prioritize the SQL files based on the priority configured in database.configuration so if a script in one jar needs to run before another, it will. After they're all sorted out, I begin running them through entityManager.createNativeQuery( ... ).executeUpdate();



Walter