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.
Agreed.
And it would be possible to store the blob in the future in the
filesystem and write a custom class which behaves like a RDBO class.
Btw: As you mention "relationship" and "foreign key". Does RDBO make a
difference between "foreign key" or "one to one"/"many to one" relationship?
I mean: one Product has many Prices. So it is modelled in the Product
class. Now in Price I would use "foreign key" or "many to one"-relationship.
Uwe
-------------------------------------------------------
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
