http://pear.php.net/bugs/search.php?cmd=display&package_name%5B0%5D=MDB2_Driver_mysql&PHPSESSID=6sh8hov6085gl1gd4s43b0k8h0 Search Results en-us pear-webmaster@lists.php.net pear-webmaster@lists.php.net hourly 1 2000-01-01T12:00+00:00 http://pear.php.net/gifs/pearsmall.gif http://pear.php.net/bugs http://pear.php.net/bugs/16781 MDB2_Driver_mysql Bug Reported by fanwar 2009-11-11T23:21:57+00:00 PHP: 5.2.3 OS: BSD Package Version: 1.4.1 Description: ------------ I'm having a difficult time with MDB2_driver_mysql and getting it to recognize transactions. I have mysql installed with InnoDB tables and when I do a $db->supports['transactions'], it keeps returning false. I checked the supported array and the values are just not set. I'm using version 1.4.1 of the driver. Anyone know what the problem may be? Here is the code I am running: Before Test script: --------------- $conn_string = "{$dbtype}://{$dbuser}:{$dbpass}@{$dbhost}/{$dbname}"; $options = array(); $options['use_transactions'] = true; $options['default_table_type'] = 'InnoDB'; $dbconn =& MDB2::singleton($conn_string, $options); if (PEAR::isError($dbconn)) { getLogger()->log("Error creating db connection: " . $dbconn->getMessage(), CritterSettings::LOG_LEVEL_CRIT); die($dbconn->getMessage()); } //BEGIN TRANSACTION HERE if ($this->db->supports('transactions')) { $this->db->beginTransaction(); } else { throw new Exception("Database is not correctly configured - transactions unsupported"); } //the exception keeps getting thrown Expected result: ---------------- I expect to get true since I am using InnoDB tables and transactions should be supported. Actual result: -------------- I get false and when I print out the supported array, it shows: Nov 11 17:08:01 [info] Array ( [sequences] => emulated [indexes] => 1 [affected_rows] => 1 [summary_functions] => 1 [order_by_text] => 1 [transactions] => [savepoints] => [current_id] => emulated [limit_queries] => 1 [LOBs] => 1 [replace] => 1 [sub_selects] => emulated [auto_increment] => 1 [primary_key] => 1 [result_introspection] => 1 [prepared_statements] => emulated [identifier_quoting] => 1 [pattern_escaping] => 1 [new_link] => 1 )]]> MDB2_Driver_mysql Bug Reported by fanwar 2009-11-11T23:21:57+00:00 PHP: 5.2.3 OS: BSD Package Version: 1.4.1 Description: ------------ I'm having a difficult time with MDB2_driver_mysql and getting it to recognize transactions. I have mysql installed with InnoDB tables and when I do a $db->supports['transactions'], it keeps returning false. I checked the supported array and the values are just not set. I'm using version 1.4.1 of the driver. Anyone know what the problem may be? Here is the code I am running: Before Test script: --------------- $conn_string = "{$dbtype}://{$dbuser}:{$dbpass}@{$dbhost}/{$dbname}"; $options = array(); $options['use_transactions'] = true; $options['default_table_type'] = 'InnoDB'; $dbconn =& MDB2::singleton($conn_string, $options); if (PEAR::isError($dbconn)) { getLogger()->log("Error creating db connection: " . $dbconn->getMessage(), CritterSettings::LOG_LEVEL_CRIT); die($dbconn->getMessage()); } //BEGIN TRANSACTION HERE if ($this->db->supports('transactions')) { $this->db->beginTransaction(); } else { throw new Exception("Database is not correctly configured - transactions unsupported"); } //the exception keeps getting thrown Expected result: ---------------- I expect to get true since I am using InnoDB tables and transactions should be supported. Actual result: -------------- I get false and when I print out the supported array, it shows: Nov 11 17:08:01 [info] Array ( [sequences] => emulated [indexes] => 1 [affected_rows] => 1 [summary_functions] => 1 [order_by_text] => 1 [transactions] => [savepoints] => [current_id] => emulated [limit_queries] => 1 [LOBs] => 1 [replace] => 1 [sub_selects] => emulated [auto_increment] => 1 [primary_key] => 1 [result_introspection] => 1 [prepared_statements] => emulated [identifier_quoting] => 1 [pattern_escaping] => 1 [new_link] => 1 )]]> 2009-11-11T23:21:57+00:00 fanwar at gmail dot com MDB2_Driver_mysql Bug http://pear.php.net/bugs/16557 MDB2_Driver_mysql Bug Reported by hschletz 2009-08-31T12:28:49+00:00 PHP: Irrelevant OS: Package Version: CVS Description: ------------ If a column has a NOT NULL attribute and a default value of NULL, getTableFieldDefinition() changes the default to '' for text columns and '0000-00-00 00:00:00' for timestamp columns. This behavior is incorrect and not portable. There is no relationship between a NOT NULL constraint and a default value. MySQL reports a NULL default because the default is NULL, not '' or '0000-00-00 00:00:00'. The attached patch leaves the null value untouched. This also reverts the patch from #12336 completely, which says: "MySQL uses '0000-00-00 00:00:00' for any timestamp fields with 'NOT NULL'. This driver should set that for any non-null fields that it finds. This will make it work better with MDB2_Schema." I disagree (the following statements also apply to text columns): - The NOT NULL / DEFAULT NULL combination is expected to force the application to provide valid input data. Depending on server SQL mode, MySQL allows NULL anyway, turns it into a pseudo-NULL value and just throws a warning. See also: http://dev.mysql.com/doc/refman/5.0/en/constraint-invalid-data.html However, this behavior only applies to MySQL and only in a specific server SQL mode. It does not change the column's definition itself and should not leak out to the application, which might run in a different environment that behaves correctly. In this case it's really up to the developer to stop doing stupid things - MySQL with default settings cannot do this for us. - As MDB2_Schema is concerned, I had to disable these implicit conversions to make it work as expected.]]> MDB2_Driver_mysql Bug Reported by hschletz 2009-08-31T12:28:49+00:00 PHP: Irrelevant OS: Package Version: CVS Description: ------------ If a column has a NOT NULL attribute and a default value of NULL, getTableFieldDefinition() changes the default to '' for text columns and '0000-00-00 00:00:00' for timestamp columns. This behavior is incorrect and not portable. There is no relationship between a NOT NULL constraint and a default value. MySQL reports a NULL default because the default is NULL, not '' or '0000-00-00 00:00:00'. The attached patch leaves the null value untouched. This also reverts the patch from #12336 completely, which says: "MySQL uses '0000-00-00 00:00:00' for any timestamp fields with 'NOT NULL'. This driver should set that for any non-null fields that it finds. This will make it work better with MDB2_Schema." I disagree (the following statements also apply to text columns): - The NOT NULL / DEFAULT NULL combination is expected to force the application to provide valid input data. Depending on server SQL mode, MySQL allows NULL anyway, turns it into a pseudo-NULL value and just throws a warning. See also: http://dev.mysql.com/doc/refman/5.0/en/constraint-invalid-data.html However, this behavior only applies to MySQL and only in a specific server SQL mode. It does not change the column's definition itself and should not leak out to the application, which might run in a different environment that behaves correctly. In this case it's really up to the developer to stop doing stupid things - MySQL with default settings cannot do this for us. - As MDB2_Schema is concerned, I had to disable these implicit conversions to make it work as expected.]]> 2009-08-31T12:28:49+00:00 holger dot schletz at web dot de MDB2_Driver_mysql Bug http://pear.php.net/bugs/16525 MDB2_Driver_mysql Feature/Change Request Reported by alsal 2009-08-14T22:43:59+00:00 PHP: 5.3.0 OS: Linux Package Version: 1.4.1 Description: ------------ Support for MYSQL's SPATIAL data formats (i.e: GEOMETRY, POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION)]]> MDB2_Driver_mysql Feature/Change Request Reported by alsal 2009-08-14T22:43:59+00:00 PHP: 5.3.0 OS: Linux Package Version: 1.4.1 Description: ------------ Support for MYSQL's SPATIAL data formats (i.e: GEOMETRY, POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION)]]> 2009-08-15T14:17:28+00:00 alan at y3h dot org MDB2_Driver_mysql Feature/Change Request http://pear.php.net/bugs/16515 MDB2_Driver_mysql Bug Reported by microtrash 2009-08-11T21:23:37+00:00 PHP: 5.3.0 OS: Windows 2003 Package Version: 1.4.1 Description: ------------ The line return $this->queryOne('SELECT LAST_INSERT_ID()', 'integer'); in method MDB2_Driver_mysql::lastInsertId(..) fails under php 5.3 returning no ID. I hacked a working version for myself by replacing that line with the following: $result = $this->_doQuery("select last_insert_id()", true); $row=mysql_fetch_array($result); $ret=$row[0]; return $ret;]]> MDB2_Driver_mysql Bug Reported by microtrash 2009-08-11T21:23:37+00:00 PHP: 5.3.0 OS: Windows 2003 Package Version: 1.4.1 Description: ------------ The line return $this->queryOne('SELECT LAST_INSERT_ID()', 'integer'); in method MDB2_Driver_mysql::lastInsertId(..) fails under php 5.3 returning no ID. I hacked a working version for myself by replacing that line with the following: $result = $this->_doQuery("select last_insert_id()", true); $row=mysql_fetch_array($result); $ret=$row[0]; return $ret;]]> 2009-08-11T21:23:37+00:00 ben at imperialwebdesigns dot com MDB2_Driver_mysql Bug