SQLHelper vs EOSchemaSynchronizationFactory
SQLHelper vs EOSchemaSynchronizationFactory
- Subject: SQLHelper vs EOSchemaSynchronizationFactory
- From: David Avendasora <email@hidden>
- Date: Tue, 14 Jan 2014 08:13:52 -0500
| Okay, I’m not sure I understand the devision-of-labor here.
When should code for generating SQL be put in a PlugIn's SQLHelper and when should it be put in the EOSchemaSynchronizationFactory?
Is there a general rule, or is it a "wherever-is-more-convienient” kind of thing?
It seems to me if the code you want SQL created for is modifying the structure of the DB, it should be in the EOSchemaSynchronizationFactory subclass, and the SQLHelper subclass would be the place for SQL that inserts/updates/deletes data and that one of them would be responsible for the common things like if identifiers should be quoted, etc.
Or, as usual, am I missing some other fundamental concept that would make this question meaningless?
Dave
—————————————————————————————
WebObjects - so easy that even Dave Avendasora can do it!™ ————————————————————————————— David Avendasora Senior Software Abuser Nekesto, Inc.
|
_______________________________________________
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