On 11/12/05 10:35 PM, John Siracusa wrote: > Things that RDBO will probably never support directly: > >> - different mappings for update and query (for example a non-updatedable >> database view for query)
Actually, I think I misunderstood that one. I think it should be in this group instead: > Things that could be built on top of RDBO fairly easily, but that are not in > the core functionality. As for this one: >> - a cache that that ensures only one instance per persisted object >> in storage, and that handles transaction isolation and rollback >> correctly. the big problem is a lack of good hooks in DBI for me to catch a commit/rollback called on a bare $dbh somewhere else in my process space. I can catch any that actually go through Rose::DB, but if some other piece of code has the same $dbh as I do (very, very likely when running under Apache::DBI) and they commit or rollback, I need to be able to catch that in order to update the object cache appropriately. Perl being Perl, I could hack something into DBI. And maybe something actually exists now, I haven't looked in a while. But the last time I checked, this was the big hold-up, and why I said I think it'll probably never be supported by RDBO (or any DBI-based Perl ORM, for that matter). -John ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
