Update of /cvsroot/secureideas/base-php4
In directory fdv4jf1.ch3.sourceforge.com:/tmp/cvs-serv1298/base-php4
I have fixed one bug out of possibly several bugs in the complex of
This particular bug here was reported at
The alerts are being archived correctly. This can be proved by
a manual SQL query.
baseDBConnect() connects with the correct database, i.e. the
But the alerts are being displayed as if it had connected with the
alert database. And why is this now a problem, and why was this
not a problem in the past?
Presumably because of a stricter behaviour in newer versions of
php or adodb:
In all of the previous versions of BASE the baseDBConnect()
function has used ONLY the baseConnect() method for archive lookups
and NOT the basePConnect() method.
baseConnect() lets only the first SQL query be executed correctly,
but none of any subsequent ones. So the subsequent queries actually
targeted the database from the still persisting connection. Which is
the alert database, and not the actually correct archive database.
RCS file: /cvsroot/secureideas/base-php4/base_qry_alert.php,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -d -r1.64 -r1.65
--- base_qry_alert.php 31 Jul 2009 22:05:51 -0000 1.64
+++ base_qry_alert.php 5 Sep 2009 20:54:49 -0000 1.65
@@ -248,6 +248,10 @@
/* Event */
$sql2 = "SELECT signature, timestamp FROM acid_event WHERE sid='".filterSql($sid)."' AND cid='".filterSql($cid)."'";
+ if ($debug_mode > 0)
+ print "<BR><BR>\n\n" . __FILE__ . ":" . __LINE__ . ": DEBUG: \$sql2 = \"$sql2\"<BR><BR>\n\n";
$result2 = $db->baseExecute($sql2);
$myrow2 = $result2->baseFetchRow();
Get latest updates about Open Source Projects, Conferences and News.