I'm working on a WebObjects project which uses a database of minor complexity, and am wrestling mentally with finding a good way to let the first run create the database.
Currently, the first run needs the EOModel's connection record to find the database (which is created my hand, but empty), and then uses Migration to read a SQL file that creates all the tables and fields. But I want a kind of "turn-key" start where, if the database doesn't exist, it gets created. My thinking so far has taken me to consider catching the exception that the missing database causes, using bare JDBC calls to create the database, and then, somehow, resuming use of the EOModel. But I learned years ago that if things are getting complicated in the WO/EOF world, I'm not doing it right; maybe there are tricks in the heart of Wonder that would help with this? I'd much appreciate any helpful ideas to carry this plan forward (or the suggestion to abandon it because it's an unnatural act!). Thanks .. Gavin
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
