[PHP-DOC] #33838 [Com]: php_manual_en.chm displaying ????? for navigation links
ID: 33838 Comment by: bo dot php dot net at email dot connaction dot net Reported By: marshall at kingstairs dot com Status: Open Bug Type: Documentation problem Operating System: Irrelevant PHP Version: Irrelevant New Comment: The problem still exists in the 23 November 2005 version... Has it been assigned to anyone?!? Previous Comments: [2005-11-12 18:28:15] bo dot php dot net at email dot connaction dot net The problem still exists in the 11 November 2005 version... [2005-10-27 03:13:16] bo dot php dot net at email dot connaction dot net The problem still exists in the 21 October 2005 version... [2005-10-21 15:23:37] bo dot php dot net at email dot connaction dot net The problem still exists in the 18 October 2005 version... [2005-10-15 19:02:38] marshall at kingstairs dot com Problem still present in 13Oct2005 version... [2005-09-27 19:07:21] marshall at kingstairs dot com Changed the OS field as the problem is not actually OS-specific . Would be nice to get this fixed, as the HtmlHelp files are not really usable because of this bug. The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/33838 -- Edit this bug report at http://bugs.php.net/?id=33838edit=1
[PHP-DOC] cvs: phpdoc /en/reference/dom reference.xml
didou Sat Nov 26 11:23:11 2005 EDT Modified files: /phpdoc/en/reference/domreference.xml Log: fix a typo found by my brother :) http://cvs.php.net/diff.php/phpdoc/en/reference/dom/reference.xml?r1=1.22r2=1.23ty=u Index: phpdoc/en/reference/dom/reference.xml diff -u phpdoc/en/reference/dom/reference.xml:1.22 phpdoc/en/reference/dom/reference.xml:1.23 --- phpdoc/en/reference/dom/reference.xml:1.22 Sun Sep 4 15:39:11 2005 +++ phpdoc/en/reference/dom/reference.xml Sat Nov 26 11:23:10 2005 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.22 $ -- +!-- $Revision: 1.23 $ -- !-- Purpose: xml -- !-- Membership: bundled, external -- @@ -898,7 +898,7 @@ entrynodeName/entry entrystring/entry entryyes/entry - entryReturns the more accurate name for the current node type/entry + entryReturns the most accurate name for the current node type/entry /row row entrynodeValue/entry
[PHP-DOC] #35417 [NEW]: PDO_MySQL docs unclear about transaction safety
From: jbarros at mail dot com Operating system: Irrelevant PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: PDO_MySQL docs unclear about transaction safety Description: http://www.php.net/manual/en/ref.pdo-mysql.php claims that MySQL tables are not transaction-safe by default; however, whether a table is transaction-safe depends on the storage engine used. The distinction is unclear and may mislead readers. Current Wording === Beware: MySQL tables do not support transactions by default. When writing transactional database code, MySQL will pretend that a transaction was initiated successfully, even when no transactional support is present. In addition, any DDL queries issued will implicitly commit any pending transactions. Improved Wording Beware: Some MySQL storage engines do not support transactions. When writing transactional database code on tables that don't support them, MySQL will pretend that a transaction was initiated successfully. In addition, any DDL queries issued will implicitly commit any pending transactions. -- Edit bug report at http://bugs.php.net/?id=35417edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=35417r=trysnapshot4 Try a CVS snapshot (php5.0): http://bugs.php.net/fix.php?id=35417r=trysnapshot50 Try a CVS snapshot (php5.1): http://bugs.php.net/fix.php?id=35417r=trysnapshot51 Fixed in CVS:http://bugs.php.net/fix.php?id=35417r=fixedcvs Fixed in release:http://bugs.php.net/fix.php?id=35417r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=35417r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=35417r=needscript Try newer version: http://bugs.php.net/fix.php?id=35417r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=35417r=support Expected behavior: http://bugs.php.net/fix.php?id=35417r=notwrong Not enough info: http://bugs.php.net/fix.php?id=35417r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=35417r=submittedtwice register_globals:http://bugs.php.net/fix.php?id=35417r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=35417r=php3 Daylight Savings:http://bugs.php.net/fix.php?id=35417r=dst IIS Stability: http://bugs.php.net/fix.php?id=35417r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=35417r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=35417r=float No Zend Extensions: http://bugs.php.net/fix.php?id=35417r=nozend MySQL Configuration Error: http://bugs.php.net/fix.php?id=35417r=mysqlcfg
[PHP-DOC] Request for clarification
Dear documentation team, The install.txt in the Windows zip file and the page http://dk2.php.net/manual/da/configuration.php#configuration.file state that the location of php.ini is searched for, among others, using the environment variable ”PHPRC”. Could you please clarify in these two documents, if the environment variable should contain the path to the directory containing php.ini or the path to the file itself, including its name? Best regards, Claus Conrad
[PHP-DOC] #35419 [NEW]: Bad example in PDOStatement:CloseCursor
From: mbuchmann at shaw dot ca Operating system: n/a PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: Bad example in PDOStatement:CloseCursor Description: Example #1 in http://ca.php.net/manual/en/function.pdostatement-closecursor.php It's supposed to create two statement handles $stmt and $otherStmt, but uses only $stmt in the -prepare() calls. Therefore $otherStmt is never defined in that code snippet, but is called Reproduce code: --- n/a Expected result: Second line of example code should return to $otherStmt -- Edit bug report at http://bugs.php.net/?id=35419edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=35419r=trysnapshot4 Try a CVS snapshot (php5.0): http://bugs.php.net/fix.php?id=35419r=trysnapshot50 Try a CVS snapshot (php5.1): http://bugs.php.net/fix.php?id=35419r=trysnapshot51 Fixed in CVS:http://bugs.php.net/fix.php?id=35419r=fixedcvs Fixed in release:http://bugs.php.net/fix.php?id=35419r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=35419r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=35419r=needscript Try newer version: http://bugs.php.net/fix.php?id=35419r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=35419r=support Expected behavior: http://bugs.php.net/fix.php?id=35419r=notwrong Not enough info: http://bugs.php.net/fix.php?id=35419r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=35419r=submittedtwice register_globals:http://bugs.php.net/fix.php?id=35419r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=35419r=php3 Daylight Savings:http://bugs.php.net/fix.php?id=35419r=dst IIS Stability: http://bugs.php.net/fix.php?id=35419r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=35419r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=35419r=float No Zend Extensions: http://bugs.php.net/fix.php?id=35419r=nozend MySQL Configuration Error: http://bugs.php.net/fix.php?id=35419r=mysqlcfg
[PHP-DOC] cvs: phpdoc /en/reference/pdo/functions PDOStatement-closeCursor.xml
dbs Sun Nov 27 01:45:15 2005 EDT
Modified files:
/phpdoc/en/reference/pdo/functions PDOStatement-closeCursor.xml
Log:
Typo -- should create a new, second statement object in example.
http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/functions/PDOStatement-closeCursor.xml?r1=1.4r2=1.5ty=u
Index: phpdoc/en/reference/pdo/functions/PDOStatement-closeCursor.xml
diff -u phpdoc/en/reference/pdo/functions/PDOStatement-closeCursor.xml:1.4
phpdoc/en/reference/pdo/functions/PDOStatement-closeCursor.xml:1.5
--- phpdoc/en/reference/pdo/functions/PDOStatement-closeCursor.xml:1.4 Sun Sep
11 02:22:26 2005
+++ phpdoc/en/reference/pdo/functions/PDOStatement-closeCursor.xml Sun Nov
27 01:45:14 2005
@@ -1,5 +1,5 @@
?xml version=1.0 encoding=iso-8859-1?
-!-- $Revision: 1.4 $ --
+!-- $Revision: 1.5 $ --
!-- Generated by xml_proto.php v2.2. Found in /scripts directory of phpdoc.
--
refentry id=function.PDOStatement-closeCursor
refnamediv
@@ -103,7 +103,7 @@
$stmt = $dbh-prepare('SELECT foo FROM bar');
/* Create a second PDOStatement object */
-$stmt = $dbh-prepare('SELECT foobaz FROM foobar');
+$otherStmt = $dbh-prepare('SELECT foobaz FROM foobar');
/* Execute the first statement */
$stmt-execute();
[PHP-DOC] #35419 [Opn-Asn]: Bad example in PDOStatement:CloseCursor
ID: 35419 Updated by: [EMAIL PROTECTED] Reported By: mbuchmann at shaw dot ca -Status: Open +Status: Assigned Bug Type: Documentation problem Operating System: n/a PHP Version: Irrelevant -Assigned To: +Assigned To: dbs New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Thanks for the catch! Previous Comments: [2005-11-27 05:18:11] mbuchmann at shaw dot ca Description: Example #1 in http://ca.php.net/manual/en/function.pdostatement-closecursor.php It's supposed to create two statement handles $stmt and $otherStmt, but uses only $stmt in the -prepare() calls. Therefore $otherStmt is never defined in that code snippet, but is called Reproduce code: --- n/a Expected result: Second line of example code should return to $otherStmt -- Edit this bug report at http://bugs.php.net/?id=35419edit=1
[PHP-DOC] #35419 [Asn-Csd]: Bad example in PDOStatement:CloseCursor
ID: 35419 Updated by: [EMAIL PROTECTED] Reported By: mbuchmann at shaw dot ca -Status: Assigned +Status: Closed Bug Type: Documentation problem Operating System: n/a PHP Version: Irrelevant Assigned To: dbs Previous Comments: [2005-11-27 07:45:45] [EMAIL PROTECTED] This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Thanks for the catch! [2005-11-27 05:18:11] mbuchmann at shaw dot ca Description: Example #1 in http://ca.php.net/manual/en/function.pdostatement-closecursor.php It's supposed to create two statement handles $stmt and $otherStmt, but uses only $stmt in the -prepare() calls. Therefore $otherStmt is never defined in that code snippet, but is called Reproduce code: --- n/a Expected result: Second line of example code should return to $otherStmt -- Edit this bug report at http://bugs.php.net/?id=35419edit=1
[PHP-DOC] cvs: phpdoc /en/reference/pdo_mysql reference.xml
dbs Sun Nov 27 01:51:43 2005 EDT Modified files: /phpdoc/en/reference/pdo_mysql reference.xml Log: Address #35417 [NEW]: PDO_MySQL docs unclear about transaction safety http://cvs.php.net/diff.php/phpdoc/en/reference/pdo_mysql/reference.xml?r1=1.6r2=1.7ty=u Index: phpdoc/en/reference/pdo_mysql/reference.xml diff -u phpdoc/en/reference/pdo_mysql/reference.xml:1.6 phpdoc/en/reference/pdo_mysql/reference.xml:1.7 --- phpdoc/en/reference/pdo_mysql/reference.xml:1.6 Thu Sep 15 16:57:51 2005 +++ phpdoc/en/reference/pdo_mysql/reference.xml Sun Nov 27 01:51:40 2005 @@ -1,5 +1,5 @@ ?xml version='1.0' encoding='iso-8859-1'? -!-- $Revision: 1.6 $ -- +!-- $Revision: 1.7 $ -- !-- Purpose: database.vendors -- !-- Membership: bundled, external, pecl -- @@ -22,10 +22,10 @@ /para warning para - Beware: MySQL tables do not support transactions by default. When - writing transactional database code, MySQL will pretend that a - transaction was initiated successfully, even when no transactional - support is present. In addition, any DDL queries issued will implicitly + Beware: Some MySQL table types (storage engines) do not support transactions. When + writing transactional database code using a table type that does not support + transactions, MySQL will pretend that a transaction was initiated successfully. + In addition, any DDL queries issued will implicitly commit any pending transactions. /para /warning
[PHP-DOC] #35417 [Opn-Csd]: PDO_MySQL docs unclear about transaction safety
ID: 35417 Updated by: [EMAIL PROTECTED] Reported By: jbarros at mail dot com -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: Irrelevant PHP Version: Irrelevant New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: [2005-11-27 01:56:55] jbarros at mail dot com Description: http://www.php.net/manual/en/ref.pdo-mysql.php claims that MySQL tables are not transaction-safe by default; however, whether a table is transaction-safe depends on the storage engine used. The distinction is unclear and may mislead readers. Current Wording === Beware: MySQL tables do not support transactions by default. When writing transactional database code, MySQL will pretend that a transaction was initiated successfully, even when no transactional support is present. In addition, any DDL queries issued will implicitly commit any pending transactions. Improved Wording Beware: Some MySQL storage engines do not support transactions. When writing transactional database code on tables that don't support them, MySQL will pretend that a transaction was initiated successfully. In addition, any DDL queries issued will implicitly commit any pending transactions. -- Edit this bug report at http://bugs.php.net/?id=35417edit=1
