-
pcxuser committed patchset 109 of module dbiwrapper to the DBIWrapper CVS repository, changing 1 files.
2008-10-22 18:39:19 UTC by pcxuser
-
I removed the code that was attempting to let fork()'ing work since it was causing issues in non-forking code and that should hopefully also resolve this issue.
I'm about to release the latest code as a stable release, FYI.
2008-10-22 18:26:40 UTC by pcxuser
-
pcxuser committed patchset 108 of module dbiwrapper to the DBIWrapper CVS repository, changing 1 files.
2008-10-22 00:26:57 UTC by pcxuser
-
pcxuser committed patchset 107 of module dbiwrapper to the DBIWrapper CVS repository, changing 2 files.
2008-10-22 00:26:23 UTC by pcxuser
-
pcxuser committed patchset 106 of module dbiwrapper to the DBIWrapper CVS repository, changing 2 files.
2008-10-21 22:10:40 UTC by pcxuser
-
apparently, when not running in a fork() environment some scripts have issues with this code, which requires the following line to be added before the return statement:
local $SIG{__DIE__} = sub { my $message = shift; if ($message !~ /Can't call method FETCH on an undefined value at/) { die $message; } };.
2007-06-05 23:55:19 UTC by nobody
-
pcxuser committed patchset 105 of module dbiwrapper to the DBIWrapper CVS repository, changing 1 files.
2007-06-02 04:57:00 UTC by pcxuser
-
applied.
2007-06-02 04:45:38 UTC by pcxuser
-
pcxuser committed patchset 104 of module dbiwrapper to the DBIWrapper CVS repository, changing 2 files.
2007-06-02 04:44:47 UTC by pcxuser
-
In the DESTROY sub in DBIWrapper.pm, add:
return if ($self->{dbh}->{InactiveDestroy});
before the $self->close;
This makes sure that if the programmer is using fork() and they have set the InactiveDestroy value for DBH that we don't close the database handle ourselves, since the instance of the DBIWrapper in the child will go out of scope and we don't want to shut down the database...
2007-06-01 19:02:58 UTC by nobody
