tag:blogger.com,1999:blog-6250399713867244328.post6119692896464269841..comments2009-12-25T22:30:50.996-05:00danielhttp://www.blogger.com/profile/01012067250242364513noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6250399713867244328.post-9820259500284595632008-11-25T13:30:00.000-05:002008-11-25T13:30:00.000-05:00http://code.google.com/p/ruby-roger-useful-functions/wiki/TableSyncer does straight mysql table syncs, as a note :)Roger Packhttp://www.blogger.com/profile/01578246846716577925noreply@blogger.comtag:blogger.com,1999:blog-6250399713867244328.post-40199149694820201232008-03-31T19:54:00.000-04:002008-03-31T19:54:00.000-04:00No, so far this is like a first-level synchronizer, as it has only one specific method of synching -- it doesn't compare records, it doesn't compare updated_at times or anything, it just asks for a list of new, changed, and deleted records from each source and loops through the source copying and saving the records appropriately.<BR/><BR/>The other thing is, for large data-sets, I haven't put in any type of paginating mechanism .. so when a large number of items need synced, it'll use a lot of memory.<BR/><BR/>Perhaps in a later version I can add these options, and of course your data sources (models) must support them as well.<BR/><BR/>Also, I may possibly put up a page where different data-source plugins can be provided, specifying what attributes and options are available .. that way you could just include a random sample of two sources and voila! Does this remind you of Apple's iSync, by chance?danielhttp://www.blogger.com/profile/01012067250242364513noreply@blogger.comtag:blogger.com,1999:blog-6250399713867244328.post-51437976059174985432008-03-29T00:19:00.000-04:002008-03-29T00:19:00.000-04:00This sounds really awesome, I'll check it out. Have you used this with any large datasets?crayzhttp://www.blogger.com/profile/11730826719862467406noreply@blogger.com