John Napiorkowski wrote: > > I also have some concerns related to any of the bits where reads and writes > are mixed (or potentially so) behind the scenes, since the replication code > has to allow the read source to potentially lag from the write source. For > me, I'd like to see more of this deferred to the storage layer, since the > replicated storage can then intercept it and do the right thing, to keep > stuff consistent. > > John >
Hm... since the replication code is so (reasonably) fragile - shouldn't there be a big caveat notice in the POD that using it with multi-create or Ordered.pm may give strange results? Or even better - is there some way to say: "I only want to work with the master now, slaves are irrelevant" ? Then the mixed read-write codepaths can be adjusted to just read back from the master and all will be well. _______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
