Hi all,
Thanks for the tips. (By the way the DataRecords are items in mailing
list data for bulk mail having CASS, DPV, NCOA, lat/lng info along
with first, last, street, city, state, zip+4, etc.)
I have made changes to cope with the infrequent big data-sets, for
example instead of valueForKey( "[EMAIL PROTECTED]" ), I
now have valueForKey( "dataList.dataRecordsCount" ) which gets count
of the dataList primaryKey in the join entity using SQL indirectly
via P.W.'s EO Clazz objectCountFor* methods.
ERXFetchSpecificationBatchIterator is great for browsing result sets
from fetch queries that may find too many rows, however, while a one-
way simple one-to-many relationship is easy to work with, what is the
approach for handling the many-to-many relationship when it comes to
adding and deleting dataRecords from the many-to-many relationship
with dataList
To recap, I have a dataList <<->> dataRecord many-to-many
relationship that uses a join entity that EOF has made invisible to
me up to now with the standard EOModeler many-to-many join which has
made convenient flattened relationships, etc. So, the _real_ design is:
DataList <->> JoinDataListDataRecord <<-> DataRecord
So, if I kill the "dataRecords" flattened relationship and its
corresponding unflattened relationship in DataList, I lose my
propogate primary key to the join table.
DataList <- joinDataListDataRecord <<-> DataRecord
Must I basically turn on the class-property diamond in the join
entity and manage the join entity itself with custom code for adding
and deleting relationships? In that case should I ditch the
flattened "dataLists" relationship in DataRecord since I am now
touching the Join entity and manipulating it myself?
Regards, Kieran
On May 12, 2006, at 5:42 PM, Guido Neitzer wrote:
On 12.05.2006, at 22:41 Uhr, Mike Schrag wrote:
Also look at ERXFetchSpecificationBatchIterator. I have not
directly used this one, but the javadoc sounds promising and it
was originally written by Max Muller, so you're pretty safe with
it I think :)
;-)
I use it often and it works great. With ERXBatchingDisplayGroup you
have to a bit careful if you sort on non entity attributes - this
may crash, depending on the version. Don't know how the current
version handles it.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%
40mac.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:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
