Honestly Anjo, I've tried this many times before, and the solution
always ended up being some kind of replication offered by the
database vendor, or something more low level. The most recent time,
it was written in .Net with ADO (gasp!). It was for SQL Server, so
it made a lot of sense. We had to compare and move millions of rows
- EOF just looked at it and had a heart attack before even starting :)
I love EOF, and use EOF for everything that fits its design happily,
but this is just not something it was designed for.
With that said - good luck!
Ken
On May 10, 2006, at 4:51 PM, Anjo Krank wrote:
Am 10.05.2006 um 22:42 schrieb Arturo Perez:
The discussion been interesting and all but why not just set up
some sort of replication scheme at the database level? I think
all the RDBMs popular on this list can do that....
Heretic.
The thing I'm doing is synching, not mere replication. It has a few
caveats, such as you need to be sure that no data is changed in
both sides, though. The same schema can also be used for offline
working, where you have - say - a laptop in the field that spools
the changed data to the main server on command.
Cheers, Anjo
_______________________________________________
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/lists%
40anderhome.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]
