On 10/6/05, Uwe Voelker <[EMAIL PROTECTED]> wrote:
> 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.
You could do it by making a new method type that loads from the file
system on demand, but that's about it. I
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.
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
Hello John,
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.
Thanks,
bye, Uwe
---
