PEAR Bug Search Results

MDB2_Driver_mysqli: Feature/Change Request 16238 [Open] BIT data type reports as unsupported

rob at tdd dot org dot uk — 2009-05-21T14:31:09+00:00

MDB2_Driver_mysqli Feature/Change Request
Reported by mightymephisto
2009-05-18T21:46:12+00:00
PHP: 5.2.5 OS: Debian Package Version: 1.5.0b2

Description:
------------
Since MySQL 5.0.3 the BIT data type is no longer treat as TINYINT(1)

http://dev.mysql.com/doc/refman/5.0/en/numeric-types.html

Please add this data type to the _mapNativeDatatype function, and to the mysql driver too.

MDB2_Driver_mysqli: Bug 12311 [Open] can't createTable() with infos from tableInfo(), if I have TIMESTAMP columns

carsten_sttgt at gmx dot de — 2007-10-23T09:39:57+00:00

MDB2_Driver_mysqli Bug
Reported by cwiedmann
2007-10-23T09:39:57+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.4.1

Description:
------------
Hello,

in addition to Bug #10488, I think there is another problem: If you have a TIMESTAMP column in MySQL you can't recreate this column with the manager module as it was, with the information from the reverse module.

Because a DEFAULT CURRENT_TIMESTAMP is illegal for a DATETIME column in MySQL, which the manager create instead of a TIMESTAMP. And yes: it's really a difference between a DATETIME and a TIMESTAMP. And if there was a TIMESTAMP, I want to have a TIMESTAMP ;-) In the constructor I told MDB2 that I want use MySQL, and so I should be able to use all basic features from this DB (without using e.g. custom types).

Another thing I'm missing:
If I create the original column with an additional "ON UPDATE CURRENT_TIMESTAMP", I don't get this info from the reverse module tableInfo(). (For this I can make a patch.)

BTW:
On this manual page [1] you can read, that MDB is creating a TIMESTAMP in MySQL, and not a DATETIME.

Regards,
Carsten

[1] http://pear.php.net/manual/en/package.database.mdb2.datatypes.php#AEN38081


Test script:
---------------
getDebugInfo());
}
PEAR::setErrorHandling(PEAR_ERROR_CALLBACK, 'printError');

$dsn      = 'mysqli://root@localhost/test';
$dbTable = 'mdb2test';

$mdb2 = MDB2::connect($dsn);
$mdb2->loadModule('Manager');
$mdb2->loadModule('Reverse', null, true);

echo 'Created table with e.g. phpMyAdmin:'.PHP_EOL;
$sql = <<exec($sql);

/* Use this for a negative test */
$sql = <<exec($sql);

echo 'Get tableInfo() from the original table:'.PHP_EOL;
$oldDefinition = $mdb2->tableInfo($dbTable);
var_dump($oldDefinition);
echo PHP_EOL;

echo 'dropTable()'.PHP_EOL.PHP_EOL;
$mdb2->dropTable($dbTable);

echo 'Show MDB2 FieldDeclaration:'.PHP_EOL;
$definition = array ();
foreach ($oldDefinition as $value) {
    $definition[$value['name']] = array(
        'type'    => $value['mdb2type'],
        'notnull' => $value['notnull'],
        'default' => $value['default'],
    );
}
echo "CREATE TABLE $dbTable (".PHP_EOL;
echo "    ".$mdb2->getFieldDeclarationList($definition).PHP_EOL;
echo ")".PHP_EOL.PHP_EOL;

echo 'createTable()'.PHP_EOL.PHP_EOL;
$mdb2->createTable($dbTable, $definition);


echo 'Get tableInfo() from the new table:'.PHP_EOL;
$newDefinition = $mdb2->tableInfo($dbTable);
var_dump($newDefinition);
echo PHP_EOL;

echo 'Are old and new tableInfo() the same?'.PHP_EOL;
var_dump($oldDefinition == $newDefinition);
echo PHP_EOL;
?>


Expected result:
----------------
No error message and the arrays $old_definition and $new_definition should be equal.


Actual result:
--------------
Created table with e.g. phpMyAdmin:
CREATE TABLE mdb2test (
    updatetime TIMESTAMP NOT NULL
    DEFAULT CURRENT_TIMESTAMP
);

Get tableInfo() from the original table:
array(1) {
  [0]=>
  array(8) {
    ["notnull"]=>
    bool(true)
    ["nativetype"]=>
    string(9) "timestamp"
    ["default"]=>
    string(17) "CURRENT_TIMESTAMP"
    ["type"]=>
    string(9) "timestamp"
    ["mdb2type"]=>
    string(9) "timestamp"
    ["name"]=>
    string(10) "updatetime"
    ["table"]=>
    string(8) "mdb2test"
    ["flags"]=>
    string(35) " not_null default_CURRENT_TIMESTAMP"
  }
}

dropTable()

Show MDB2 FieldDeclaration:
CREATE TABLE mdb2test (
    updatetime DATETIME DEFAULT CURRENT_TIMESTAMP NOT NULL
)

createTable()

_doQuery: [Error message: Could not execute statement]
[Last executed query: CREATE  TABLE mdb2test (updatetime DATETIME DEFAULT CURRENT_TIMESTAMP NOT NULL)]
[Native code: 1067]
[Native message: Fehlerhafter Vorgabewert (DEFAULT) fÃ¼r 'updatetime']

MDB2_Driver_mysqli: Bug 12038 [Verified] Memory Leak when an error occures on an insert

2007-09-19T15:48:34+00:00

MDB2_Driver_mysqli Bug
Reported by henningh
2007-09-12T16:16:47+00:00
PHP: 5.2.3 OS: Linux & Windows Package Version: 1.4.1

Description:
------------
Hi,
I think there's a bug in the error handling when an error occures on an insert. The error is in my case an failure on the insert because the value I try to insert is an unique one.
The error handling works fine, the problem is, that an memory leak occures. In the test script below, everything is fine, as long as there is no data in the database. The memory usage is fine.
But when i try to add a duplicate, an error is raised, as well as the memory and I get fatal error after about 855 tries. I tells me that the memory is exhausted (8MB Limit).

Tried the same thin with an own native implemtation of mysqli and everything was fine.

A friend of mine tried the script below on his Windows machine with the same effects. The only difference between the linux and the windows test is, that the memory leek does not end in an exhausted memory error.

I'm not quite sure, if this is not a generell MDB2 problem, i had no time to check this with other database types.

Test script:
---------------
 0,'result_buffering' =>false));
if(PEAR::isError($mdb2)){
	die($mdb2->getUserInfo());
}
$a=0;
for($i=1;$i<=1000;$i++){
	echo 'TESTINSERT - DEBUG - Insert INTO testtable(test_id) VALUES('.$a.') 
';
	echo 'TESTINSERT - DEBUG - Iteration: '. $i . ' Memory useage at start: '.memory_get_usage().'
';
	$result = $mdb2->query('Insert INTO testtable(test_id) VALUES('.$a.')');
	if(PEAR::isError($result)){
		echo $result->getUserInfo() . '
';
	}
	$a = $a +1;
}
?>

Expected result:
----------------
In this version of the script you should see error messages and at the end on the second run of the script an "memory exhausted" error, when runnning with 8 mb.

Tried to track down this bug, but could not get far with it. As far as i have seen, the memory raises only, if an error occures and is handled in the MDB2.php


Actual result:
--------------
Linux:

TESTINSERT - DEBUG - Insert INTO testtable(test_id) VALUES(0)
TESTINSERT - DEBUG - Iteration: 1 Memory useage at start: 1075564
_doQuery: [Error message: Could not execute statement] [Last executed query: Insert INTO testtable(test_id) VALUES(0)] [Native code: 1062] [Native message: Duplicate entry '0' for key 2]
TESTINSERT - DEBUG - Insert INTO testtable(test_id) VALUES(1)
TESTINSERT - DEBUG - Iteration: 2 Memory useage at start: 1092244
_doQuery: [Error message: Could not execute statement] [Last executed query: Insert INTO testtable(test_id) VALUES(1)] [Native code: 1062] [Native message: Duplicate entry '1' for key 2]
TESTINSERT - DEBUG - Insert INTO testtable(test_id) VALUES(2)
TESTINSERT - DEBUG - Iteration: 3 Memory useage at start: 1100856
_doQuery: [Error message: Could not execute statement] [Last executed query: Insert INTO testtable(test_id) VALUES(2)] [Native code: 1062] [Native message: Duplicate entry '2' for key 2] 

...

_doQuery: [Error message: Could not execute statement] [Last executed query: Insert INTO testtable(test_id) VALUES(852)] [Native code: 1062] [Native message: Duplicate entry '852' for key 2]
TESTINSERT - DEBUG - Insert INTO testtable(test_id) VALUES(853)
TESTINSERT - DEBUG - Iteration: 854 Memory useage at start: 8378792
_doQuery: [Error message: Could not execute statement] [Last executed query: Insert INTO testtable(test_id) VALUES(853)] [Native code: 1062] [Native message: Duplicate entry '853' for key 2]
TESTINSERT - DEBUG - Insert INTO testtable(test_id) VALUES(854)
TESTINSERT - DEBUG - Iteration: 855 Memory useage at start: 8387344

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 207 bytes) in /opt/lampp/lib/php/MDB2.php on line 972



Windows:

TESTINSERT - DEBUG - Insert INTO testtable(test_id) VALUES(0)
TESTINSERT - DEBUG - Iteration: 1 Memory useage at start: 24690688
_doQuery: [Error message: Could not execute statement] [Last executed query: Insert INTO testtable(test_id) VALUES(0)] [Native code: 1062] [Native message: Duplicate entry '0' for key 1]

...

TESTINSERT - DEBUG - Insert INTO testtable(test_id) VALUES(999)
TESTINSERT - DEBUG - Iteration: 1000 Memory useage at start: 33779712
_doQuery: [Error message: Could not execute statement] [Last executed query: Insert INTO testtable(test_id) VALUES(999)] [Native code: 1062] [Native message: Duplicate entry '999' for key 1]