Re: Migrations problem with FrontBase
Re: Migrations problem with FrontBase
- Subject: Re: Migrations problem with FrontBase
- From: "Cheong Hee (Gmail)" <email@hidden>
- Date: Wed, 19 Dec 2012 12:16:30 +0800
|
Found this original WO doc to share and hope it
helps. Not sure if this still hold water after integrating with
Wonder:
"When
resolving a prototype name, Enterprise Objects Framework looks for prototypes in
EO<adaptor-name>Prototypes, then in
EOPrototypes, and finally in the adaptor for your model. This
search path allows you to override the prototypes provided by each adaptor.
Furthermore, if you don't want to use the adaptor-defined prototypes at all, you
can hide them. Create an entity named EOPrototypesToHide. For
each prototype you want to hide, create an attribute with that name; you don't
need to specify other attribute properties."
Cheers
Cheong Hee
----- Original Message -----
Sent: Wednesday, December 19, 2012 1:06
AM
Subject: Re: Migrations problem with
FrontBase
Hi guys,
For a reason beyond my
skills, the application seems to be indeed using the MySQL prototypes instead
of FrontBase's to create the _dbupdater table. My model surely has the
FrontBase prototypes selected, but this seems not to influence the prototypes
choice by ERXMigrator or ERXJDBCMigrationLock.
So my solution was to create the _dbupdater table by hand and
populate it with the models I use. After this intervention the migrations
worked again.
But the question remains, from where
does ERXMigrator take the prototypes
information?
Cheers,
Angelo
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden