And the logs say (let's not jump to conclusions)?

And what do the logs say? See "DEBUGGING" in the DBI documentation (and check your database's logs). I would strongly hesitate to blame Class::DBI just yet.

UPDATE: *sigh* but before you do that, which version of Class::DBI do you have? Do you have transactions turned on? What does update return? Do you have any update triggers?

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Comment on And the logs say (let's not jump to conclusions)?

Replies are listed 'Best First'.
Re: And the logs say (let's not jump to conclusions)? by TVSET (Chaplain) on Mar 11, 2004 at 12:43 UTC
Thanks a lot! ;) The problem was that out of the code that I copy-pasted (as usual). Stupid me called one method get(). Class::DBI's behavior became very logical when I figured it out. Leonid Mamtchenkov aka TVSET	[reply]

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.