Re: Database Independence
Re: Database Independence
- Subject: Re: Database Independence
- From: Anjo Krank <email@hidden>
- Date: Tue, 19 Feb 2008 09:29:59 +0100
I presume it is a bit more clever than just looking for an entity
called EOJDBCAdaptorPrototypes and will somehow look for an entity
with the JDBC plugin's name in it or something?
We had this in Wonder for ages now... for us the lookup is:
EOJDBCPostgresqlPrototypes
EOJDBCPrototypes
EOPrototypes
At startup we combine a prototype entity with all the attributes,
first write wins, so you can keep common ones in EOPrototypes and only
refine in EOJDBCPostgresqlPrototypes. Then all prototypes are applied
to the model. With 5.4 I have no idea. I assume it's similar.
Cheers, Anjo
Am 19.02.2008 um 08:45 schrieb Andrew Lindesay:
Hello;
I see the following which looks good, but doesn't really explain the
mechanics -- does anybody know how this has changed?
Radar #5084084
Enhance EOF prototyping support
Description:
Enhance EOModel prototyping support to make it recognize the
Database Management System used just like it does with the plugin
support.
Workaround:
This has been fixed in WebObjects 5.4.
I presume it is a bit more clever than just looking for an entity
called EOJDBCAdaptorPrototypes and will somehow look for an entity
with the JDBC plugin's name in it or something?
cheers
___
Andrew Lindesay
technology : www.lindesay.co.nz
business : www.silvereye.co.nz
_______________________________________________
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
_______________________________________________
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