On 10/6/05, Uwe Voelker <[EMAIL PROTECTED]> wrote: > Class::DBI has the concept of column groups (Primary, Essential, All). > > Is there a similar thing in RDBO? I would like to exclude some blobs > from a table, which should only be loaded when explicitly called.
In order to add a generic column grouping solution, every column accessor method would have to know whether it's had its value fetched, and would have to go fetch it on demand if it has not. That'd be one more piece of state information per-column, per-object that RDBO would have to maintain internally, and it'd add significant complexity to every accessor method. To mitigate that complexity, accessors could be wrapped, but there's a pretty big performance cost for that. In the specific case of a table with one big BLOB column, it's usually more efficient to move the BLOBs to another table and then link to it with a "one to one" relationship or foreign key. That will get you the behavior you want, and will also probably be more efficient in the database itself. -John ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
