On Dec 29, 2007, at 12:47 AM, Peter Edwards wrote:
I'd think twice about mastering your images in the database.
It depends on data volumes and number of simultaneous accesses, but
the
easiest is to keep them in a directory hierarchy under Unix with a
normal
backup to protect them, running an
AP
>> What do you think? Two classes for the table? One for admin functions
>> which has the LONGBLOB in it and one for the web app (Catalyst) which
>> doesn't?
>>
>> Is there a better trick for this kind of thing?
MS
>Typical SQL "best practice" is to use two tables ... the meta-data
>table (or ma
> What do you think? Two classes for the table? One for admin functions
> which has the LONGBLOB in it and one for the web app (Catalyst) which
> doesn't?
>
> Is there a better trick for this kind of thing?
Typical SQL "best practice" is to use two tables ... the meta-data
table (or main table) an
