Re: DBI Conundrum Using CGI::App

Replies are listed 'Best First'.
Re^2: DBI Conundrum Using CGI::App by waltw (Acolyte) on Jul 06, 2006 at 20:02 UTC
Thank you, David, but with SQLite I have auto-commit. However, your response kicked several synapses into gear and I took a look at permissions..... I'm so red-faced! My directory was 755 and the webserver had read-only permission. I'm fixed and all is working as it should be. Pardon me for posting a non-problem! Appreciatively, Walt	[reply]
Re^2: DBI Conundrum Using CGI::App by shmem (Chancellor) on Jul 06, 2006 at 19:48 UTC
`$dbh->commit`? Oh, yes. But before I'd do a `$sth->finish`. --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply] [d/l] [select]
Re^3: DBI Conundrum Using CGI::App by Hue-Bond (Priest) on Jul 06, 2006 at 20:05 UTC
Quoting the DBI documentation: `rarely needed` `frequently overused` `you should not normally need to call it explicitly` `internal "housekeeping" method that is rarely needed` And I don't see why it should be used here. -- David Serrano	[reply]
Re^3: DBI Conundrum Using CGI::App by jZed (Prior) on Jul 06, 2006 at 20:03 UTC
$sth->finish() is relevant only to SELECT and other data-returning calls and only then when the data has not been fully fetched. It has no relevance to an UPDATE statement and should not be used in this case.	[reply]