Re: Framework EOModel Question
Re: Framework EOModel Question
- Subject: Re: Framework EOModel Question
- From: LD <email@hidden>
- Date: Fri, 5 Aug 2005 11:06:56 +1000
Hi there,
On 05/08/2005, at 2:10 AM, Chuck Hill wrote:
On Aug 3, 2005, at 11:15 PM, LD wrote:
The framework isn't db agnostic (currently)
Tsk Tsk ;-)
Be patient with me; I'm getting there (slowly) ;-)
because the EOModels in the framework are currently tied to
postgres specific column attribute types. Any tips on making the
models db agnostic?
EOPrototypes, as Kieran pointed out. A model without prototypes is,
um, dumb.
Point taken. I'll get around to utilising PW... just getting as
comfortable as I can with WO first.
A reusable framework without prototypes is not reusable. See
Practical WebObjects pages 45 - 55 for a discussion of this and
code. There is some very superficial discussion in the EOModeler docs.
Cheers. The discussion in the book was helpful... on towards
utilising EOJDBCPrototypes entity/models.
I'm utilising the postgres 'serial' type for auto-incrementing
primary keys...
I can't see how EOF is going to be happy about that.
Hence the use of the PostgresqlPlugIn.framework. Works well (with my
slight alteration to the plugin).
If anyone's using PostgreSQL successfully without the plugin, I'm all
ears!
To promote reusability you should avoid non standard, DB specific
features.
then there's timestamp types and so on...
Those are usually pretty standard.
Certainly, incorporating prototypes will help with both of these...
Cheers.
with regards,
--
LD
_______________________________________________
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