Peter Flanigan wrote:
Tony Winslow wrote:
Danny Warren wrote:
It would be helpful if you could post a code sample. I am sure
someone could spot it quickly that way (more eyes, etc etc).
Check to make sure the first argument to your search call is truly
undef, and make sure you are pas
Peter Flanigan wrote:
Tony Winslow wrote:
Danny Warren wrote:
It would be helpful if you could post a code sample. I am sure
someone could spot it quickly that way (more eyes, etc etc).
Check to make sure the first argument to your search call is truly
undef, and make sure you are pas
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
> I am writing a small catalyst application for online maintenance of leave
> records at the office. I need to ensure that a dept head is not flooded with
> all the leave applications, but gets only those pertaining to his dept. I
> have a users table and a leave_application table. The first table
Hi,
I am writing a small catalyst application for online maintenance of leave
records at the office. I need to ensure that a dept head is not flooded with
all the leave applications, but gets only those pertaining to his dept. I
have a users table and a leave_application table. The first table con
Peter Flanigan wrote:
Tony Winslow wrote:
Danny Warren wrote:
It would be helpful if you could post a code sample. I am sure
someone could spot it quickly that way (more eyes, etc etc).
Check to make sure the first argument to your search call is truly
undef, and make sure you are pas
Tony Winslow wrote:
> Danny Warren wrote:
>> It would be helpful if you could post a code sample. I am sure
>> someone could spot it quickly that way (more eyes, etc etc).
>>
>> Check to make sure the first argument to your search call is truly
>> undef, and make sure you are passing your array of
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
