Re: [Newbie] WO 5.2/mySQL/EOModeler Alert No Reason Provided
Re: [Newbie] WO 5.2/mySQL/EOModeler Alert No Reason Provided
- Subject: Re: [Newbie] WO 5.2/mySQL/EOModeler Alert No Reason Provided
- From: Art Isbell <email@hidden>
- Date: Thu, 5 Jun 2003 09:41:43 -1000
On Thursday, June 5, 2003, at 08:16 AM, Jess Bowers wrote:
I'm getting an oddly confusing, vague and frustrating error in
EOModeler
when trying to synchronize my model with the database.
Alert : No Reason Provided.
When I delete the tables in the DB, then run Generate SQL and re-create
them, then run synchronize schema, it generally works (sometimes there
are
messages, usually about the "drop constraint" -- which is confusing,
since I
don't really know a lick of SQL -- isn't EO/JDBC supposed to handle
this for
me?)
It's not uncommon to get database errors when creating a database
schema from SQL generated by EOModeler. In your example, a "drop
constraint" error could be caused by no such constraint existing in the
database, so there's nothing to drop, yet you sent (via EOModeler) the
SQL instructing the database to drop the constraint. If you're
familiar with the existing database schema, such errors can usually be
avoided by your choice of what SQL you ask EOModeler to generate and
execute. The series of check boxes in EOModeler's SQL Generation panel
control the SQL generated. You might have been able to avoid the "drop
constraint" error by unchecking "Drop Primary Key Support". Such
errors have never prevented schema generation in the databases that
I've worked with, but these don't include MySQL.
Reverse-engineering an eomodel from and synchronizing an eomodel with
an existing database schema can be more problematic. I think this is
because database support for schema manipulation operations is not
nearly so standardized as that for the usual data manipulation
operations. I don't know how well MySQL or its JDBC driver supports
schema manipulation, so this might be part of the problem.
You might find that you must change the database schema manually using
MySQL tools and apply the identical changes to your eomodel manually
using EOModeler rather than trying to use EOModeler's SQL generation
and schema synchronization features.
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.