PEAR is archived and read-only

This mirror preserves historical PEAR package releases and metadata so existing references remain available.

Home » Database » MDB2 » Bug #9024

Various uninitialized variables

Details

Submitted2006-10-14 10:00 UTC
Fromjo at durchholz dot org
Assignedquipo
StatusClosed
PackageMDB2
PHP VersionIrrelevant
OSAny
Roadmaps(Not assigned)

Comments

[2006-10-14 10:00 UTC] jo at durchholz dot org

Description:
------------
Here's a list of uninitialized variables in MDB2 and used MDB2 drivers (ibase, mssql, mysql, and pgsql) that running an MDB2-based project through Eclipse uncovered:

Variable Path File Line
--------------------------------------------------------
$created_objects MDB2 Schema.php 450
$result MDB2/Driver ibase.php 325
$results MDB2/Driver/Manager mssql.php 217
$results MDB2/Driver/Manager mssql.php 231
$default_table_type MDB2/Driver mysql.php 159
$match MDB2/Driver pgsql.php 244

These look like real bugs to me, i.e. code that wasn't updated after changes elsewhere ($created_objects, $result), variable name typos ($results), trying to access the wrong variable ($default_table_type), or overlooked variable initialization ($match).
(Splitting this up into a separate bug report per package would do these bugs far too much honor.)

[2006-10-15 07:03 UTC] jo at durchholz dot org

Sorry, I forgot the package versions, here they are:
ibase: 1.2.1 (current)
mssql: 1.1.0 (current)
mysql: 1.2.2 (current)
pgsql: 1.2.2 (current)

For Lorenzo: I'm not sure what exactly went wrong, maybe there was a copy&paste error involved. The real uninitialized $match is at line 680.

I'm unable to check back via CVS right now. I'd have to configure it to use CVS in one part of the project, where everything else uses SVN, and I'm not sure how to do that without damaging the existing project (yesterday was my first day with Eclipse...).
I'll start doing CVS checkouts once I'm more familiar with Eclipse :-)