It sounds to me like sharing the model would be less effort. Rather than use rawRowsForSQL you can just make regular fetch specs and tell them to fetch raw rows. You might get more data back than you need, but all the join and name translation etc will be handled for you.
Chuck On 2016-02-21, 6:40 AM, "[email protected] on behalf of ocs.cz" <[email protected] on behalf of [email protected]> wrote: >Hello there, > >my web app should occassionally import from an external DB (a database created >and maintained by another WO-based application). Just import, and only >low-level dictionaries at that, never full-fledged EO-objects. Probably >though, the imported tables would be rather big, it would be needed to join >them (i.e., import also attributes accessible through a relationship), etc. > >Having so far no experience with accessing another DB, I wonder. > >Would I gain anything of importance by sharing the model and using EOF for the >import (in which case, due to them joins, I am afraid I would have to go as >low as to EOUtilities.rawRowsForSQL anyway), or would you rather, in this >special case, skip EOF altogether and go DIY at the JDBC level? (The latter >approach would lead to reading in the other app's model anyway, but without >using the EOF stack over it, just to manually translate entity and property >names to tables/columns, nothing more.) > >Thanks, >OC > > > _______________________________________________ >Do not post admin requests to the list. They will be ignored. >Webobjects-dev mailing list ([email protected]) >Help/Unsubscribe/Update your Subscription: >https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com > >This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
