#46249 [Opn]: pdo_pgsql always fill in NULL for empty BLOB

2008-10-12 Thread hswong3i at gmail dot com
 ID:   46249
 User updated by:  hswong3i at gmail dot com
 Reported By:  hswong3i at gmail dot com
 Status:   Open
 Bug Type: PDO related
 Operating System: Debian
 PHP Version:  5.2.6
 Assigned To:  felipe
 New Comment:

It is now result as:

string(23) "Test normal BLOB insert"

string(15) "This is�a test."

string(15) "This is�a test."

bool(true)

string(21) "Test NULL BLOB insert"

NULL

string(0) ""

bool(false)

string(22) "Test empty BLOB insert"

string(0) ""

string(0) ""

bool(true)


Previous Comments:


[2008-10-13 02:31:42] hswong3i at gmail dot com

Bug still exists, but preform in another way... Please try the
following code snippet:

");
  var_dump($msg);
  print("");
}

function db_insert($sql, $data) {
  global $active_db;
  $stmt = $active_db->prepare($sql);
  $blob = fopen('php://memory', 'a');
  fwrite($blob, $data);
  rewind($blob);
  $stmt->bindParam(':blob1', $blob, PDO::PARAM_LOB);
  $stmt->execute();
  $id = $active_db->lastInsertId('test_one_blob_id_seq');
  return $id;
}

function db_select($sql, $id) {
  global $active_db;
  $sql = 'SELECT * FROM "test_one_blob" WHERE "id" = :id';
  $stmt = $active_db->prepare($sql);
  $stmt->bindParam(':id', $id);
  $stmt->execute();
  return $stmt->fetch(PDO::FETCH_ASSOC);
}

$active_db = new PDO('pgsql:host=localhost dbname=DRUPAL_7', 'root',
'CHANGE', array(PDO::ATTR_STRINGIFY_FETCHES => TRUE));

// Test normal BLOB insert
$data = "This is\000a test.";
$id = db_insert('INSERT INTO "test_one_blob" ("blob1") VALUES
(:blob1)', $data);
$return = db_select('SELECT * FROM "test_one_blob" WHERE "id" = :id',
$id);
_var_dump("Test normal BLOB insert");
_var_dump($data);
_var_dump($return['blob1']);
_var_dump($data === $return['blob1']);

// Test NULL BLOB insert
$data = NULL;
$id = db_insert('INSERT INTO "test_one_blob" ("blob1") VALUES
(:blob1)', $data);
$return = db_select('SELECT * FROM "test_one_blob" WHERE "id" = :id',
$id);
_var_dump("Test NULL BLOB insert");
_var_dump($data);
_var_dump($return['blob1']);
_var_dump($data === $return['blob1']);

// Test empty BLOB insert
$data = "";
$id = db_insert('INSERT INTO "test_one_blob" ("blob1") VALUES
(:blob1)', $data);
$return = db_select('SELECT * FROM "test_one_blob" WHERE "id" = :id',
$id);
_var_dump("Test empty BLOB insert");
_var_dump($data);
_var_dump($return['blob1']);
_var_dump($data === $return['blob1']);

?>



[2008-10-12 17:44:50] hswong3i at gmail dot com

@felipe: Yes I did. I give a compare with cvs.php.net log message, and
check if my PHP package coming with the fix. Fix is already included,
#46249 is fixed but than buggy for #46274 as mentioned :S

I try both PHP in CLI and Apache2.2. BLOB INSERT/UPDATE are successful
in both cases, but fetching NULL and empty string are both buggy...



[2008-10-12 16:51:05] [EMAIL PROTECTED]

Do you have tried after 13:03:31 2008 UTC? I've commited a complete fix
to these issue in this time.

Thanks.



[2008-10-12 16:39:57] hswong3i at gmail dot com

I try for both PHP5.2 and 5.3 from http://snaps.php.net/ (they both
coming with the fix). They are now able to handle NULL and empty string
BLOB INSERT/UPDATE. Thanks for the work.

BTW, it is now generate another issue that should belongs to
http://bugs.php.net/bug.php?id=46274. Whenever fetching NULL or empty
BLOB content from DB apache will crash with Segmentation fault. Maybe we
still need some love for that :S



[2008-10-11 19:05:59] [EMAIL PROTECTED]

This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.





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/46249

-- 
Edit this bug report at http://bugs.php.net/?id=46249&edit=1



#46249 [Csd->Opn]: pdo_pgsql always fill in NULL for empty BLOB

2008-10-12 Thread hswong3i at gmail dot com
 ID:   46249
 User updated by:  hswong3i at gmail dot com
 Reported By:  hswong3i at gmail dot com
-Status:   Closed
+Status:   Open
 Bug Type: PDO related
 Operating System: Debian
 PHP Version:  5.2.6
 Assigned To:  felipe
 New Comment:

Bug still exists, but preform in another way... Please try the
following code snippet:

");
  var_dump($msg);
  print("");
}

function db_insert($sql, $data) {
  global $active_db;
  $stmt = $active_db->prepare($sql);
  $blob = fopen('php://memory', 'a');
  fwrite($blob, $data);
  rewind($blob);
  $stmt->bindParam(':blob1', $blob, PDO::PARAM_LOB);
  $stmt->execute();
  $id = $active_db->lastInsertId('test_one_blob_id_seq');
  return $id;
}

function db_select($sql, $id) {
  global $active_db;
  $sql = 'SELECT * FROM "test_one_blob" WHERE "id" = :id';
  $stmt = $active_db->prepare($sql);
  $stmt->bindParam(':id', $id);
  $stmt->execute();
  return $stmt->fetch(PDO::FETCH_ASSOC);
}

$active_db = new PDO('pgsql:host=localhost dbname=DRUPAL_7', 'root',
'CHANGE', array(PDO::ATTR_STRINGIFY_FETCHES => TRUE));

// Test normal BLOB insert
$data = "This is\000a test.";
$id = db_insert('INSERT INTO "test_one_blob" ("blob1") VALUES
(:blob1)', $data);
$return = db_select('SELECT * FROM "test_one_blob" WHERE "id" = :id',
$id);
_var_dump("Test normal BLOB insert");
_var_dump($data);
_var_dump($return['blob1']);
_var_dump($data === $return['blob1']);

// Test NULL BLOB insert
$data = NULL;
$id = db_insert('INSERT INTO "test_one_blob" ("blob1") VALUES
(:blob1)', $data);
$return = db_select('SELECT * FROM "test_one_blob" WHERE "id" = :id',
$id);
_var_dump("Test NULL BLOB insert");
_var_dump($data);
_var_dump($return['blob1']);
_var_dump($data === $return['blob1']);

// Test empty BLOB insert
$data = "";
$id = db_insert('INSERT INTO "test_one_blob" ("blob1") VALUES
(:blob1)', $data);
$return = db_select('SELECT * FROM "test_one_blob" WHERE "id" = :id',
$id);
_var_dump("Test empty BLOB insert");
_var_dump($data);
_var_dump($return['blob1']);
_var_dump($data === $return['blob1']);

?>


Previous Comments:


[2008-10-12 17:44:50] hswong3i at gmail dot com

@felipe: Yes I did. I give a compare with cvs.php.net log message, and
check if my PHP package coming with the fix. Fix is already included,
#46249 is fixed but than buggy for #46274 as mentioned :S

I try both PHP in CLI and Apache2.2. BLOB INSERT/UPDATE are successful
in both cases, but fetching NULL and empty string are both buggy...



[2008-10-12 16:51:05] [EMAIL PROTECTED]

Do you have tried after 13:03:31 2008 UTC? I've commited a complete fix
to these issue in this time.

Thanks.



[2008-10-12 16:39:57] hswong3i at gmail dot com

I try for both PHP5.2 and 5.3 from http://snaps.php.net/ (they both
coming with the fix). They are now able to handle NULL and empty string
BLOB INSERT/UPDATE. Thanks for the work.

BTW, it is now generate another issue that should belongs to
http://bugs.php.net/bug.php?id=46274. Whenever fetching NULL or empty
BLOB content from DB apache will crash with Segmentation fault. Maybe we
still need some love for that :S



[2008-10-11 19:05:59] [EMAIL PROTECTED]

This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.





[2008-10-11 11:47:35] [EMAIL PROTECTED]

Oh sorry, you're right. I can reproduce it.



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/46249

-- 
Edit this bug report at http://bugs.php.net/?id=46249&edit=1



#46284 [Opn->Bgs]: Error parsing C:\Programmi\PHP\php.ini

2008-10-12 Thread tularis
 ID:   46284
 Updated by:   [EMAIL PROTECTED]
 Reported By:  iok2 at libero dot it
-Status:   Open
+Status:   Bogus
 Bug Type: *Configuration Issues
 Operating System: Windows XP
 PHP Version:  5.2.6
 New Comment:

Sorry, but your problem does not imply a bug in PHP itself.  For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system is not the
appropriate forum for asking support questions.  Due to the volume
of reports we can not explain in detail here why your report is not
a bug.  The support channels will be able to provide an explanation
for you.

Thank you for your interest in PHP.




Previous Comments:


[2008-10-12 22:42:12] iok2 at libero dot it

.



[2008-10-12 22:38:17] iok2 at libero dot it

Description:

I've a problem with PHP 5.2.6 configuration. I use Apache 2.2.6 with
this configuration for PHP in httpd.conf:

PHPIniDir "C:/Programmi/PHP/"
LoadModule php5_module "C:/Programmi/PHP/php5apache2_2.dll"


In the php.ini file I've this instruction in the line 3:
PHPIniDir "C:\\Programmi\\PHP\\"

If I do not use that instruction (PHPIniDir "C:\\Programmi\\PHP\\" , or
similar path) in the php.ini file, PHP don't work, but I've the parsing
error message at the start of Apache service.

I've PHP path environment variable enabled.
How can I fix the parsing error?

Reproduce code:
---
[PHP]

PHPInidir "C:\\Programmi\\PHP\\"

;;;
; About php.ini   ;
;;;
; This file controls many aspects of PHP's behavior.  In order for PHP
to
; read it, it must be named 'php.ini'.  PHP looks for it in the
current
; working directory, in the path designated by the environment
variable
; PHPRC, and in the path that was defined in compile time (in that
order).
; Under Windows, the compile-time path is the Windows directory.  The
; path in which the php.ini file is looked for can be overridden using
; the -c argument in command line mode.
;
; The syntax of the file is extremely simple.  Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably
guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
;
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from
FOO=bar.
;
; The value can be a string, a number, a PHP constant (e.g. E_ALL or
M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an
expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
;
; Expressions in the INI file are limited to bitwise operators and
parentheses:
; |bitwise OR
; &bitwise AND
; ~bitwise NOT
; !boolean NOT
;
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
;
; An empty string can be denoted by simply not writing anything after
the equal
; sign, or by using the None keyword:
;
;  foo = ; sets foo to an empty string
;  foo = none; sets foo to an empty string
;  foo = "none"  ; sets foo to the string 'none'
;
; If you use constants in your value, and these constants belong to a
; dynamically loaded extension (either a PHP extension or a Zend
extension),
; you may only use these constants *after* the line that loads the
extension.
; 
;
;;;
; About this file ;
;;;
; This is the recommended, PHP 5-style version of the php.ini-dist
file.  It
; sets some non standard settings, that make PHP more efficient, more
secure,
; and encourage cleaner coding.
;
; The price is that with these settings, PHP may be incompatible with
some
; applications, and sometimes, more difficult to develop with.  Using
this
; file is warmly recommended for production sites.  As all of the
changes from
; the standard settings are thoroughly documented, you can go over each
one,
; and decide whether you want to use it or not.
;
; For general information about the php.ini file, please consult the
php.ini-dist
; file, included in your PHP distribution.
;
; This file is different from the php.ini-dist file in the fact that it
features
; different values for several directives, in order to improve
performance, while
; possibly breaking compatibility with the standard out-of-the-box
behavior of
; PHP.  Please make sure you read what's different, and modify your
scripts
; accordingly, if you decide to use this file instead.
;
; - register_long_arrays = Off [Performance]
; Disables registration of the older (and deprecated) long
predefined array
; variables ($HTTP_*_VARS).  Instead, use the superglobals that
were
; introduced in PHP 4.1.0
; - display_errors = Off  

#46284 [Opn]: Error parsing C:\Programmi\PHP\php.ini

2008-10-12 Thread iok2 at libero dot it
 ID:   46284
 User updated by:  iok2 at libero dot it
-Summary:  Error parsing C:\Programs\PHP\php.ini
 Reported By:  iok2 at libero dot it
 Status:   Open
 Bug Type: *Configuration Issues
 Operating System: Windows XP
 PHP Version:  5.2.6
 New Comment:

.


Previous Comments:


[2008-10-12 22:38:17] iok2 at libero dot it

Description:

I've a problem with PHP 5.2.6 configuration. I use Apache 2.2.6 with
this configuration for PHP in httpd.conf:

PHPIniDir "C:/Programmi/PHP/"
LoadModule php5_module "C:/Programmi/PHP/php5apache2_2.dll"


In the php.ini file I've this instruction in the line 3:
PHPIniDir "C:\\Programmi\\PHP\\"

If I do not use that instruction (PHPIniDir "C:\\Programmi\\PHP\\" , or
similar path) in the php.ini file, PHP don't work, but I've the parsing
error message at the start of Apache service.

I've PHP path environment variable enabled.
How can I fix the parsing error?

Reproduce code:
---
[PHP]

PHPInidir "C:\\Programmi\\PHP\\"

;;;
; About php.ini   ;
;;;
; This file controls many aspects of PHP's behavior.  In order for PHP
to
; read it, it must be named 'php.ini'.  PHP looks for it in the
current
; working directory, in the path designated by the environment
variable
; PHPRC, and in the path that was defined in compile time (in that
order).
; Under Windows, the compile-time path is the Windows directory.  The
; path in which the php.ini file is looked for can be overridden using
; the -c argument in command line mode.
;
; The syntax of the file is extremely simple.  Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably
guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
;
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from
FOO=bar.
;
; The value can be a string, a number, a PHP constant (e.g. E_ALL or
M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an
expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
;
; Expressions in the INI file are limited to bitwise operators and
parentheses:
; |bitwise OR
; &bitwise AND
; ~bitwise NOT
; !boolean NOT
;
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
;
; An empty string can be denoted by simply not writing anything after
the equal
; sign, or by using the None keyword:
;
;  foo = ; sets foo to an empty string
;  foo = none; sets foo to an empty string
;  foo = "none"  ; sets foo to the string 'none'
;
; If you use constants in your value, and these constants belong to a
; dynamically loaded extension (either a PHP extension or a Zend
extension),
; you may only use these constants *after* the line that loads the
extension.
; 
;
;;;
; About this file ;
;;;
; This is the recommended, PHP 5-style version of the php.ini-dist
file.  It
; sets some non standard settings, that make PHP more efficient, more
secure,
; and encourage cleaner coding.
;
; The price is that with these settings, PHP may be incompatible with
some
; applications, and sometimes, more difficult to develop with.  Using
this
; file is warmly recommended for production sites.  As all of the
changes from
; the standard settings are thoroughly documented, you can go over each
one,
; and decide whether you want to use it or not.
;
; For general information about the php.ini file, please consult the
php.ini-dist
; file, included in your PHP distribution.
;
; This file is different from the php.ini-dist file in the fact that it
features
; different values for several directives, in order to improve
performance, while
; possibly breaking compatibility with the standard out-of-the-box
behavior of
; PHP.  Please make sure you read what's different, and modify your
scripts
; accordingly, if you decide to use this file instead.
;
; - register_long_arrays = Off [Performance]
; Disables registration of the older (and deprecated) long
predefined array
; variables ($HTTP_*_VARS).  Instead, use the superglobals that
were
; introduced in PHP 4.1.0
; - display_errors = Off   [Security]
; With this directive set to off, errors that occur during the
execution of
; scripts will no longer be displayed as a part of the script
output, and thus,
; will no longer be exposed to remote users.  With some errors, the
error message
; content may expose information about your script, web server, or
database
; server that may be exploitable for hacking.  Production sites
should have this
; directive set to off.
; - log_errors = On[Security]
; This directive complements t

#46284 [NEW]: Error parsing C:\Programs\PHP\php.ini

2008-10-12 Thread iok2 at libero dot it
From: iok2 at libero dot it
Operating system: Windows XP
PHP version:  5.2.6
PHP Bug Type: *Configuration Issues
Bug description:  Error parsing C:\Programs\PHP\php.ini

Description:

I've a problem with PHP 5.2.6 configuration. I use Apache 2.2.6 with this
configuration for PHP in httpd.conf:

PHPIniDir "C:/Programmi/PHP/"
LoadModule php5_module "C:/Programmi/PHP/php5apache2_2.dll"


In the php.ini file I've this instruction in the line 3:
PHPIniDir "C:\\Programmi\\PHP\\"

If I do not use that instruction (PHPIniDir "C:\\Programmi\\PHP\\" , or
similar path) in the php.ini file, PHP don't work, but I've the parsing
error message at the start of Apache service.

I've PHP path environment variable enabled.
How can I fix the parsing error?

Reproduce code:
---
[PHP]

PHPInidir "C:\\Programmi\\PHP\\"

;;;
; About php.ini   ;
;;;
; This file controls many aspects of PHP's behavior.  In order for PHP to
; read it, it must be named 'php.ini'.  PHP looks for it in the current
; working directory, in the path designated by the environment variable
; PHPRC, and in the path that was defined in compile time (in that
order).
; Under Windows, the compile-time path is the Windows directory.  The
; path in which the php.ini file is looked for can be overridden using
; the -c argument in command line mode.
;
; The syntax of the file is extremely simple.  Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably
guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
;
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from
FOO=bar.
;
; The value can be a string, a number, a PHP constant (e.g. E_ALL or
M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an
expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
;
; Expressions in the INI file are limited to bitwise operators and
parentheses:
; |bitwise OR
; &bitwise AND
; ~bitwise NOT
; !boolean NOT
;
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
;
; An empty string can be denoted by simply not writing anything after the
equal
; sign, or by using the None keyword:
;
;  foo = ; sets foo to an empty string
;  foo = none; sets foo to an empty string
;  foo = "none"  ; sets foo to the string 'none'
;
; If you use constants in your value, and these constants belong to a
; dynamically loaded extension (either a PHP extension or a Zend
extension),
; you may only use these constants *after* the line that loads the
extension.
; 
;
;;;
; About this file ;
;;;
; This is the recommended, PHP 5-style version of the php.ini-dist file. 
It
; sets some non standard settings, that make PHP more efficient, more
secure,
; and encourage cleaner coding.
;
; The price is that with these settings, PHP may be incompatible with
some
; applications, and sometimes, more difficult to develop with.  Using
this
; file is warmly recommended for production sites.  As all of the changes
from
; the standard settings are thoroughly documented, you can go over each
one,
; and decide whether you want to use it or not.
;
; For general information about the php.ini file, please consult the
php.ini-dist
; file, included in your PHP distribution.
;
; This file is different from the php.ini-dist file in the fact that it
features
; different values for several directives, in order to improve
performance, while
; possibly breaking compatibility with the standard out-of-the-box
behavior of
; PHP.  Please make sure you read what's different, and modify your
scripts
; accordingly, if you decide to use this file instead.
;
; - register_long_arrays = Off [Performance]
; Disables registration of the older (and deprecated) long predefined
array
; variables ($HTTP_*_VARS).  Instead, use the superglobals that were
; introduced in PHP 4.1.0
; - display_errors = Off   [Security]
; With this directive set to off, errors that occur during the
execution of
; scripts will no longer be displayed as a part of the script output,
and thus,
; will no longer be exposed to remote users.  With some errors, the
error message
; content may expose information about your script, web server, or
database
; server that may be exploitable for hacking.  Production sites should
have this
; directive set to off.
; - log_errors = On[Security]
; This directive complements the above one.  Any errors that occur
during the
; execution of your script will be logged (typically, to your server's
error log,
; but can be configured in several ways).  Along with setting
display_errors to off,
; this setup gives you t

#46283 [NEW]: array_merge_recursive() Warning recursion detected in...

2008-10-12 Thread name at email dot com
From: name at email dot com
Operating system: windows xp sp3
PHP version:  5.2.6
PHP Bug Type: Scripting Engine problem
Bug description:  array_merge_recursive() Warning recursion detected in...

Description:

Calling array_merge_recursive() produces an unclear warning ("recursion
detected in"...) and seems to be breaking the script. The above happens if
two conditions are met:

1. there is a private/protected data member in the object (see code).
2. the merged arrays contain at least one same string as key.
 
* please note: following code reproduces this problem on the latest snaps
of both 5.2.6 and 5.3

Reproduce code:
---
class A {
  private $variable;
  public function __construct() {
$this->variable = 'foo';
  }
}

$x = new A;
$b = array_merge_recursive(array("name"=>$x),array("name"=>$x));
var_dump($b);


Expected result:

see 'Actual result' below...

Actual result:
--
array(1) {
  ["name"]=>
  array(1) {
["�A�variable"]=>
array(2) {
  [0]=>
  string(3) "foo"
  [1]=>
  string(3) "foo"
}
  }
}


-- 
Edit bug report at http://bugs.php.net/?id=46283&edit=1
-- 
Try a CVS snapshot (PHP 5.2): 
http://bugs.php.net/fix.php?id=46283&r=trysnapshot52
Try a CVS snapshot (PHP 5.3): 
http://bugs.php.net/fix.php?id=46283&r=trysnapshot53
Try a CVS snapshot (PHP 6.0): 
http://bugs.php.net/fix.php?id=46283&r=trysnapshot60
Fixed in CVS: http://bugs.php.net/fix.php?id=46283&r=fixedcvs
Fixed in release: 
http://bugs.php.net/fix.php?id=46283&r=alreadyfixed
Need backtrace:   http://bugs.php.net/fix.php?id=46283&r=needtrace
Need Reproduce Script:http://bugs.php.net/fix.php?id=46283&r=needscript
Try newer version:http://bugs.php.net/fix.php?id=46283&r=oldversion
Not developer issue:  http://bugs.php.net/fix.php?id=46283&r=support
Expected behavior:http://bugs.php.net/fix.php?id=46283&r=notwrong
Not enough info:  
http://bugs.php.net/fix.php?id=46283&r=notenoughinfo
Submitted twice:  
http://bugs.php.net/fix.php?id=46283&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=46283&r=globals
PHP 4 support discontinued:   http://bugs.php.net/fix.php?id=46283&r=php4
Daylight Savings: http://bugs.php.net/fix.php?id=46283&r=dst
IIS Stability:http://bugs.php.net/fix.php?id=46283&r=isapi
Install GNU Sed:  http://bugs.php.net/fix.php?id=46283&r=gnused
Floating point limitations:   http://bugs.php.net/fix.php?id=46283&r=float
No Zend Extensions:   http://bugs.php.net/fix.php?id=46283&r=nozend
MySQL Configuration Error:http://bugs.php.net/fix.php?id=46283&r=mysqlcfg



#46278 [Asn]: Unsupported Oracle version! 11.1

2008-10-12 Thread sixd
 ID:   46278
 Updated by:   [EMAIL PROTECTED]
 Reported By:  Fedora at FamilleCollet dot com
 Status:   Assigned
-Bug Type: OCI8 related
+Bug Type: PDO related
 Operating System: Linux (Fedora 9)
 PHP Version:  5.2CVS-2008-10-12 (snap)
 Assigned To:  cjorcl
 New Comment:

Stas merged a fix to 5.3 & 6 for this last week.


Previous Comments:


[2008-10-12 11:08:36] [EMAIL PROTECTED]

Chris, please take a look.



[2008-10-12 10:40:06] Fedora at FamilleCollet dot com

Description:

When trying to build against oracle instantclient 11.1.0.6 with

--with-pdo-oci=shared,instantclient,/usr,11.1.0.6

I got the "Unsupported Oracle version! 11.1" error.

Reading the ext/pdo_oci/config.m4

I see 
  PDO_OCI_VERSION="`echo $PDO_OCI_IC_VERS | cut -d. -f1-2`"
which give 11.1

And  
  case $PDO_OCI_VERSION in
9.x|10.x|11.x)

Probaly  using 
  PDO_OCI_VERSION="`echo $PDO_OCI_IC_VERS | cut -d. -f1`".x

Will give better results ;)

Well and phpinfo still display "PDO Driver for OCI 8 and later" (when 8
is no mor supported).

Reproduce code:
---
-

Expected result:

-

Actual result:
--
-





-- 
Edit this bug report at http://bugs.php.net/?id=46278&edit=1



#46249 [Csd]: pdo_pgsql always fill in NULL for empty BLOB

2008-10-12 Thread hswong3i at gmail dot com
 ID:   46249
 User updated by:  hswong3i at gmail dot com
 Reported By:  hswong3i at gmail dot com
 Status:   Closed
 Bug Type: PDO related
 Operating System: Debian
 PHP Version:  5.2.6
 Assigned To:  felipe
 New Comment:

@felipe: Yes I did. I give a compare with cvs.php.net log message, and
check if my PHP package coming with the fix. Fix is already included,
#46249 is fixed but than buggy for #46274 as mentioned :S

I try both PHP in CLI and Apache2.2. BLOB INSERT/UPDATE are successful
in both cases, but fetching NULL and empty string are both buggy...


Previous Comments:


[2008-10-12 16:51:05] [EMAIL PROTECTED]

Do you have tried after 13:03:31 2008 UTC? I've commited a complete fix
to these issue in this time.

Thanks.



[2008-10-12 16:39:57] hswong3i at gmail dot com

I try for both PHP5.2 and 5.3 from http://snaps.php.net/ (they both
coming with the fix). They are now able to handle NULL and empty string
BLOB INSERT/UPDATE. Thanks for the work.

BTW, it is now generate another issue that should belongs to
http://bugs.php.net/bug.php?id=46274. Whenever fetching NULL or empty
BLOB content from DB apache will crash with Segmentation fault. Maybe we
still need some love for that :S



[2008-10-11 19:05:59] [EMAIL PROTECTED]

This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.





[2008-10-11 11:47:35] [EMAIL PROTECTED]

Oh sorry, you're right. I can reproduce it.



[2008-10-11 06:47:47] hswong3i at gmail dot com

According to http://www.php.net/manual/en/pdo.lobs.php, using PDO for
BLOB INSERT/UPDATE should come with:
1. bindParam/bindColumn
2. PDO::PARAM_LOB
3. stream API, e.g. fopen(), fwrite(), rewind(), etc.

You may try to insert other value though you code snippet. The value
should also NOT able to insert into PostgreSQL...

The bug reproduction code in
http://drupal.org/node/316095#comment-1047830 is using pdo_pgsql
directly. The db_insert() used is just a fake clone of Drupal CVS HEAD
function with simplified programming logic.



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/46249

-- 
Edit this bug report at http://bugs.php.net/?id=46249&edit=1



#46249 [Csd]: pdo_pgsql always fill in NULL for empty BLOB

2008-10-12 Thread felipe
 ID:   46249
 Updated by:   [EMAIL PROTECTED]
 Reported By:  hswong3i at gmail dot com
 Status:   Closed
 Bug Type: PDO related
 Operating System: Debian
 PHP Version:  5.2.6
 Assigned To:  felipe
 New Comment:

Do you have tried after 13:03:31 2008 UTC? I've commited a complete fix
to these issue in this time.

Thanks.


Previous Comments:


[2008-10-12 16:39:57] hswong3i at gmail dot com

I try for both PHP5.2 and 5.3 from http://snaps.php.net/ (they both
coming with the fix). They are now able to handle NULL and empty string
BLOB INSERT/UPDATE. Thanks for the work.

BTW, it is now generate another issue that should belongs to
http://bugs.php.net/bug.php?id=46274. Whenever fetching NULL or empty
BLOB content from DB apache will crash with Segmentation fault. Maybe we
still need some love for that :S



[2008-10-11 19:05:59] [EMAIL PROTECTED]

This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.





[2008-10-11 11:47:35] [EMAIL PROTECTED]

Oh sorry, you're right. I can reproduce it.



[2008-10-11 06:47:47] hswong3i at gmail dot com

According to http://www.php.net/manual/en/pdo.lobs.php, using PDO for
BLOB INSERT/UPDATE should come with:
1. bindParam/bindColumn
2. PDO::PARAM_LOB
3. stream API, e.g. fopen(), fwrite(), rewind(), etc.

You may try to insert other value though you code snippet. The value
should also NOT able to insert into PostgreSQL...

The bug reproduction code in
http://drupal.org/node/316095#comment-1047830 is using pdo_pgsql
directly. The db_insert() used is just a fake clone of Drupal CVS HEAD
function with simplified programming logic.



[2008-10-11 00:26:16] [EMAIL PROTECTED]

I can't reproduce using 5.3CVS:

$db = new PDO('pgsql:host=localhost dbname=test', 'foo', 'bar',
array(PDO::ATTR_STRINGIFY_FETCHES => TRUE));

$stmt = $db->prepare("INSERT INTO test_one_blob (blob1) VALUES (?)");
$stmt->execute(array(''));
var_dump($db->errorinfo());

$stmt = $db->prepare("INSERT INTO test_one_blob (blob1) VALUES
(:foo)");
$x = '';
$stmt->bindParam(':foo', $x);
$stmt->execute();
var_dump($db->errorinfo());

$stmt = $db->query("INSERT INTO test_one_blob (blob1) VALUES ('')");
$stmt->execute();


teste=> select * from test_one_blob where blob1 is null;
 id | blob1 
+---
(0 registros)


Do you have tested using PDO directly, without Drupal's db_insert()?



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/46249

-- 
Edit this bug report at http://bugs.php.net/?id=46249&edit=1



#46249 [Csd]: pdo_pgsql always fill in NULL for empty BLOB

2008-10-12 Thread hswong3i at gmail dot com
 ID:   46249
 User updated by:  hswong3i at gmail dot com
 Reported By:  hswong3i at gmail dot com
 Status:   Closed
 Bug Type: PDO related
 Operating System: Debian
 PHP Version:  5.2.6
 Assigned To:  felipe
 New Comment:

I try for both PHP5.2 and 5.3 from http://snaps.php.net/ (they both
coming with the fix). They are now able to handle NULL and empty string
BLOB INSERT/UPDATE. Thanks for the work.

BTW, it is now generate another issue that should belongs to
http://bugs.php.net/bug.php?id=46274. Whenever fetching NULL or empty
BLOB content from DB apache will crash with Segmentation fault. Maybe we
still need some love for that :S


Previous Comments:


[2008-10-11 19:05:59] [EMAIL PROTECTED]

This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.





[2008-10-11 11:47:35] [EMAIL PROTECTED]

Oh sorry, you're right. I can reproduce it.



[2008-10-11 06:47:47] hswong3i at gmail dot com

According to http://www.php.net/manual/en/pdo.lobs.php, using PDO for
BLOB INSERT/UPDATE should come with:
1. bindParam/bindColumn
2. PDO::PARAM_LOB
3. stream API, e.g. fopen(), fwrite(), rewind(), etc.

You may try to insert other value though you code snippet. The value
should also NOT able to insert into PostgreSQL...

The bug reproduction code in
http://drupal.org/node/316095#comment-1047830 is using pdo_pgsql
directly. The db_insert() used is just a fake clone of Drupal CVS HEAD
function with simplified programming logic.



[2008-10-11 00:26:16] [EMAIL PROTECTED]

I can't reproduce using 5.3CVS:

$db = new PDO('pgsql:host=localhost dbname=test', 'foo', 'bar',
array(PDO::ATTR_STRINGIFY_FETCHES => TRUE));

$stmt = $db->prepare("INSERT INTO test_one_blob (blob1) VALUES (?)");
$stmt->execute(array(''));
var_dump($db->errorinfo());

$stmt = $db->prepare("INSERT INTO test_one_blob (blob1) VALUES
(:foo)");
$x = '';
$stmt->bindParam(':foo', $x);
$stmt->execute();
var_dump($db->errorinfo());

$stmt = $db->query("INSERT INTO test_one_blob (blob1) VALUES ('')");
$stmt->execute();


teste=> select * from test_one_blob where blob1 is null;
 id | blob1 
+---
(0 registros)


Do you have tested using PDO directly, without Drupal's db_insert()?



[2008-10-07 18:00:22] hswong3i at gmail dot com

Description:

When pdo_pgsql working with:
  1. BLOB field,
  2. running INSERT/UPDATE queries, and
  3. BLOB value with empty string ''

It will always fill NULL into database and so result as buggy.
INSERT/UPDATE BLOB value with NULL will function correctly.

P.S. pdo_mysql is NOT buggy when running with similar programming
logic, empty string pass into database correctly. Tested with PHP5.2.6
and PHP5.3-dev, both are buggy.

Reproduce code:
---
Please refer to http://drupal.org/node/316095#comment-1047830 for more
information.

Expected result:

Empty string should fill into database correctly.

Actual result:
--
Empty string is now stored as NULL.





-- 
Edit this bug report at http://bugs.php.net/?id=46249&edit=1



#46282 [NEW]: Corrupt DBF When Using DATE

2008-10-12 Thread mattias dot geniar at gmail dot com
From: mattias dot geniar at gmail dot com
Operating system: CentOS 5.2
PHP version:  5.2.6
PHP Bug Type: dBase related
Bug description:  Corrupt DBF When Using DATE

Description:

Creating a dBase file with a DATE-field type, will corrupt the database.
Work-around as for now is to use a CHAR-type and convert it later
manually.

This bug is similar to #42261, which dates back to August 2007.

Reproduce code:
---



Expected result:

A simple database with 5 lines, where DATE, Name & Email are entered
correctly.

Actual result:
--
The code above will create file called "test.dbf", which is corrupted when
opening it with any normal DBF-viewer (CDBF, DBF Manager, ...). If the
DATE-field is replaced with a CHAR-field, all works fine. Date-format is
taken from the PHP.NET website and confirmed by the dBase-format.

-- 
Edit bug report at http://bugs.php.net/?id=46282&edit=1
-- 
Try a CVS snapshot (PHP 5.2): 
http://bugs.php.net/fix.php?id=46282&r=trysnapshot52
Try a CVS snapshot (PHP 5.3): 
http://bugs.php.net/fix.php?id=46282&r=trysnapshot53
Try a CVS snapshot (PHP 6.0): 
http://bugs.php.net/fix.php?id=46282&r=trysnapshot60
Fixed in CVS: http://bugs.php.net/fix.php?id=46282&r=fixedcvs
Fixed in release: 
http://bugs.php.net/fix.php?id=46282&r=alreadyfixed
Need backtrace:   http://bugs.php.net/fix.php?id=46282&r=needtrace
Need Reproduce Script:http://bugs.php.net/fix.php?id=46282&r=needscript
Try newer version:http://bugs.php.net/fix.php?id=46282&r=oldversion
Not developer issue:  http://bugs.php.net/fix.php?id=46282&r=support
Expected behavior:http://bugs.php.net/fix.php?id=46282&r=notwrong
Not enough info:  
http://bugs.php.net/fix.php?id=46282&r=notenoughinfo
Submitted twice:  
http://bugs.php.net/fix.php?id=46282&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=46282&r=globals
PHP 4 support discontinued:   http://bugs.php.net/fix.php?id=46282&r=php4
Daylight Savings: http://bugs.php.net/fix.php?id=46282&r=dst
IIS Stability:http://bugs.php.net/fix.php?id=46282&r=isapi
Install GNU Sed:  http://bugs.php.net/fix.php?id=46282&r=gnused
Floating point limitations:   http://bugs.php.net/fix.php?id=46282&r=float
No Zend Extensions:   http://bugs.php.net/fix.php?id=46282&r=nozend
MySQL Configuration Error:http://bugs.php.net/fix.php?id=46282&r=mysqlcfg



#46274 [Asn->Csd]: pdo_pgsql - Segfault when using PDO::ATTR_STRINGIFY_FETCHES and blob

2008-10-12 Thread felipe
 ID:   46274
 Updated by:   [EMAIL PROTECTED]
 Reported By:  [EMAIL PROTECTED]
-Status:   Assigned
+Status:   Closed
 Bug Type: PDO related
 Operating System: Linux
 PHP Version:  5.3CVS-2008-10-11 (CVS)
 Assigned To:  felipe
 New Comment:

This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.




Previous Comments:


[2008-10-12 01:23:39] [EMAIL PROTECTED]

Oh, that isn't fixed yet.



[2008-10-11 19:05:50] [EMAIL PROTECTED]

This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.





[2008-10-11 00:52:24] [EMAIL PROTECTED]

Description:

See below.

Reproduce code:
---
 TRUE));

$res = $db->prepare("SELECT blob1 from test_one_blob");
$res->execute();
var_dump($res->fetch(PDO::FETCH_NUM));

Actual result:
--
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb77e26d0 (LWP 18255)]
0x0839a800 in _php_stream_stat (stream=0x88b4500, ssb=0xbfac2124,
tsrm_ls=0x8767070) at /home/felipe/dev/php5/main/streams/streams.c:693
693 if (stream->wrapper && stream->wrapper->wops->stream_stat != 
NULL)
{
(gdb) bt
#0  0x0839a800 in _php_stream_stat (stream=0x88b4500, ssb=0xbfac2124,
tsrm_ls=0x8767070) at /home/felipe/dev/php5/main/streams/streams.c:693
#1  0x0839b9f0 in _php_stream_copy_to_mem (src=0x88b4500,
buf=0xbfac21f0, maxlen=0, persistent=0, __php_stream_call_depth=0, 
__zend_filename=0x86bbd58
"/home/felipe/dev/php5/ext/pdo/pdo_stmt.c", __zend_lineno=608,
__zend_orig_filename=0x0, __zend_orig_lineno=0, tsrm_ls=0x8767070)
at /home/felipe/dev/php5/main/streams/streams.c:1254
#2  0x08130c5d in fetch_value (stmt=0x88b3bcc, dest=0x88b394c, colno=0,
type_override=0x0, tsrm_ls=0x8767070) at
/home/felipe/dev/php5/ext/pdo/pdo_stmt.c:608
#3  0x08132732 in do_fetch (stmt=0x88b3bcc, do_bind=1,
return_value=0x88b39e4, how=PDO_FETCH_NUM, ori=PDO_FETCH_ORI_NEXT,
offset=0, return_all=0x0, 
tsrm_ls=0x8767070) at
/home/felipe/dev/php5/ext/pdo/pdo_stmt.c:1123
#4  0x081338c6 in zim_PDOStatement_fetch (ht=1, return_value=0x88b39e4,
return_value_ptr=0x0, this_ptr=0x88b2318, return_value_used=1,
tsrm_ls=0x8767070)
at /home/felipe/dev/php5/ext/pdo/pdo_stmt.c:1401
#5  0x0843efbd in zend_do_fcall_common_helper_SPEC
(execute_data=0x88e1674, tsrm_ls=0x8767070) at
/home/felipe/dev/php5/Zend/zend_vm_execute.h:315
#6  0x0844017b in ZEND_DO_FCALL_BY_NAME_SPEC_HANDLER
(execute_data=0x88e1674, tsrm_ls=0x8767070) at
/home/felipe/dev/php5/Zend/zend_vm_execute.h:428
#7  0x0843dd6c in execute (op_array=0x88b2ad0, tsrm_ls=0x8767070) at
/home/felipe/dev/php5/Zend/zend_vm_execute.h:104
#8  0x0840e59b in zend_execute_scripts (type=8, tsrm_ls=0x8767070,
retval=0x0, file_count=3) at /home/felipe/dev/php5/Zend/zend.c:1197
#9  0x0837ecbe in php_execute_script (primary_file=0xbfac48b8,
tsrm_ls=0x8767070) at /home/felipe/dev/php5/main/main.c:2080
#10 0x084add03 in main (argc=2, argv=0xbfac4a14) at
/home/felipe/dev/php5/sapi/cli/php_cli.c:1130






-- 
Edit this bug report at http://bugs.php.net/?id=46274&edit=1



#46281 [NEW]: Introduce Threading into PHP

2008-10-12 Thread boujin at yahoo dot com
From: boujin at yahoo dot com
Operating system: Irrelevant
PHP version:  5.2.6
PHP Bug Type: Feature/Change Request
Bug description:  Introduce Threading into PHP

Description:

Threading could be introduced to take advantage of our multi-core
processors.

Also, to be able to access different databases or sites at the same time.

Reproduce code:
---
Irrelevant

Expected result:

Irrelevant

Actual result:
--
Irrelevant

-- 
Edit bug report at http://bugs.php.net/?id=46281&edit=1
-- 
Try a CVS snapshot (PHP 5.2): 
http://bugs.php.net/fix.php?id=46281&r=trysnapshot52
Try a CVS snapshot (PHP 5.3): 
http://bugs.php.net/fix.php?id=46281&r=trysnapshot53
Try a CVS snapshot (PHP 6.0): 
http://bugs.php.net/fix.php?id=46281&r=trysnapshot60
Fixed in CVS: http://bugs.php.net/fix.php?id=46281&r=fixedcvs
Fixed in release: 
http://bugs.php.net/fix.php?id=46281&r=alreadyfixed
Need backtrace:   http://bugs.php.net/fix.php?id=46281&r=needtrace
Need Reproduce Script:http://bugs.php.net/fix.php?id=46281&r=needscript
Try newer version:http://bugs.php.net/fix.php?id=46281&r=oldversion
Not developer issue:  http://bugs.php.net/fix.php?id=46281&r=support
Expected behavior:http://bugs.php.net/fix.php?id=46281&r=notwrong
Not enough info:  
http://bugs.php.net/fix.php?id=46281&r=notenoughinfo
Submitted twice:  
http://bugs.php.net/fix.php?id=46281&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=46281&r=globals
PHP 4 support discontinued:   http://bugs.php.net/fix.php?id=46281&r=php4
Daylight Savings: http://bugs.php.net/fix.php?id=46281&r=dst
IIS Stability:http://bugs.php.net/fix.php?id=46281&r=isapi
Install GNU Sed:  http://bugs.php.net/fix.php?id=46281&r=gnused
Floating point limitations:   http://bugs.php.net/fix.php?id=46281&r=float
No Zend Extensions:   http://bugs.php.net/fix.php?id=46281&r=nozend
MySQL Configuration Error:http://bugs.php.net/fix.php?id=46281&r=mysqlcfg



#46280 [NEW]: uasort bug

2008-10-12 Thread goodfriends0092004 at yahoo dot com
From: goodfriends0092004 at yahoo dot com
Operating system: windows
PHP version:  5.2.6
PHP Bug Type: Unknown/Other Function
Bug description:  uasort bug

Description:

i found a bug of uasort function

Reproduce code:
---
$x = array(1,1,1,1,1,1,1,'a'=>1);
uasort($x,create_function('$a,$b', 'return 0;'));
var_dump($x);

Expected result:

array
  5 => int 1
  6 => int 1
  'a' => int 1
  4 => int 1
  3 => int 1
  1 => int 1
  2 => int 1
  0 => int 1




-- 
Edit bug report at http://bugs.php.net/?id=46280&edit=1
-- 
Try a CVS snapshot (PHP 5.2): 
http://bugs.php.net/fix.php?id=46280&r=trysnapshot52
Try a CVS snapshot (PHP 5.3): 
http://bugs.php.net/fix.php?id=46280&r=trysnapshot53
Try a CVS snapshot (PHP 6.0): 
http://bugs.php.net/fix.php?id=46280&r=trysnapshot60
Fixed in CVS: http://bugs.php.net/fix.php?id=46280&r=fixedcvs
Fixed in release: 
http://bugs.php.net/fix.php?id=46280&r=alreadyfixed
Need backtrace:   http://bugs.php.net/fix.php?id=46280&r=needtrace
Need Reproduce Script:http://bugs.php.net/fix.php?id=46280&r=needscript
Try newer version:http://bugs.php.net/fix.php?id=46280&r=oldversion
Not developer issue:  http://bugs.php.net/fix.php?id=46280&r=support
Expected behavior:http://bugs.php.net/fix.php?id=46280&r=notwrong
Not enough info:  
http://bugs.php.net/fix.php?id=46280&r=notenoughinfo
Submitted twice:  
http://bugs.php.net/fix.php?id=46280&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=46280&r=globals
PHP 4 support discontinued:   http://bugs.php.net/fix.php?id=46280&r=php4
Daylight Savings: http://bugs.php.net/fix.php?id=46280&r=dst
IIS Stability:http://bugs.php.net/fix.php?id=46280&r=isapi
Install GNU Sed:  http://bugs.php.net/fix.php?id=46280&r=gnused
Floating point limitations:   http://bugs.php.net/fix.php?id=46280&r=float
No Zend Extensions:   http://bugs.php.net/fix.php?id=46280&r=nozend
MySQL Configuration Error:http://bugs.php.net/fix.php?id=46280&r=mysqlcfg



#45046 [Com]: Missing php5servlet.dll in PECL Collection package

2008-10-12 Thread amit dot sanon at gmail dot com
 ID:   45046
 Comment by:   amit dot sanon at gmail dot com
 Reported By:  steve at thebroughs dot com
 Status:   No Feedback
 Bug Type: Servlet related
 Operating System: Windows
 PHP Version:  5.2.6
 Assigned To:  pajoye
 New Comment:

The files are still missing from 
http://snaps.php.net/win32/php5.2-win32-latest.zip

Can someone please check and add the files php_java.dll and
php5servlet.dll to the pecl collection package


Previous Comments:


[2008-07-23 01:00:01] php-bugs at lists dot php dot net

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".



[2008-07-15 06:32:32] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php5.2-latest.tar.gz
 
For Windows (zip):
 
  http://snaps.php.net/win32/php5.2-win32-latest.zip

For Windows (installer):

  http://snaps.php.net/win32/php5.2-win32-installer-latest.msi





[2008-07-15 00:04:45] [EMAIL PROTECTED]

Pierre, fix.



[2008-05-22 09:22:33] [EMAIL PROTECTED]

It wasn't in the 5.2.5 zip either, it was in this
pecl-5.2.5-Win32-1.zip instead. For some reason the same PECL
collection for 5.2.6 does not contain it.



[2008-05-20 07:08:50] steve at thebroughs dot com

Description:

I'm trying to install PHP into a TOMCAT server and have read a number
of articles that refer to php5servlet.dll. This file is available in
V5.2.5 but is not included the latest release. Is this file missing, or
has it been replaced with another DLL?






-- 
Edit this bug report at http://bugs.php.net/?id=45046&edit=1



#46279 [NEW]: next() behaviour inside foreach changed

2008-10-12 Thread jozefchutka at gmail dot com
From: jozefchutka at gmail dot com
Operating system: windows
PHP version:  5.2.6
PHP Bug Type: *General Issues
Bug description:  next() behaviour inside foreach changed

Description:

there is a bug in 5.2.6 causing unexpected results when using next()
function indisde foreach. Results from php 5.1, or 4.x are as expected.

Reproduce code:
---
";
}
?>

Expected result:

a next is: b
b next is: c
c next is: d
d next is: e
e next is: 

Actual result:
--
a next is: c
b next is: d
c next is: e
d next is:
e next is: 

-- 
Edit bug report at http://bugs.php.net/?id=46279&edit=1
-- 
Try a CVS snapshot (PHP 5.2): 
http://bugs.php.net/fix.php?id=46279&r=trysnapshot52
Try a CVS snapshot (PHP 5.3): 
http://bugs.php.net/fix.php?id=46279&r=trysnapshot53
Try a CVS snapshot (PHP 6.0): 
http://bugs.php.net/fix.php?id=46279&r=trysnapshot60
Fixed in CVS: http://bugs.php.net/fix.php?id=46279&r=fixedcvs
Fixed in release: 
http://bugs.php.net/fix.php?id=46279&r=alreadyfixed
Need backtrace:   http://bugs.php.net/fix.php?id=46279&r=needtrace
Need Reproduce Script:http://bugs.php.net/fix.php?id=46279&r=needscript
Try newer version:http://bugs.php.net/fix.php?id=46279&r=oldversion
Not developer issue:  http://bugs.php.net/fix.php?id=46279&r=support
Expected behavior:http://bugs.php.net/fix.php?id=46279&r=notwrong
Not enough info:  
http://bugs.php.net/fix.php?id=46279&r=notenoughinfo
Submitted twice:  
http://bugs.php.net/fix.php?id=46279&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=46279&r=globals
PHP 4 support discontinued:   http://bugs.php.net/fix.php?id=46279&r=php4
Daylight Savings: http://bugs.php.net/fix.php?id=46279&r=dst
IIS Stability:http://bugs.php.net/fix.php?id=46279&r=isapi
Install GNU Sed:  http://bugs.php.net/fix.php?id=46279&r=gnused
Floating point limitations:   http://bugs.php.net/fix.php?id=46279&r=float
No Zend Extensions:   http://bugs.php.net/fix.php?id=46279&r=nozend
MySQL Configuration Error:http://bugs.php.net/fix.php?id=46279&r=mysqlcfg



#46278 [Opn->Asn]: Unsupported Oracle version! 11.1

2008-10-12 Thread johannes
 ID:   46278
 Updated by:   [EMAIL PROTECTED]
 Reported By:  Fedora at FamilleCollet dot com
-Status:   Open
+Status:   Assigned
 Bug Type: OCI8 related
 Operating System: Linux (Fedora 9)
 PHP Version:  5.2CVS-2008-10-12 (snap)
-Assigned To:  
+Assigned To:  cjorcl
 New Comment:

Chris, please take a look.


Previous Comments:


[2008-10-12 10:40:06] Fedora at FamilleCollet dot com

Description:

When trying to build against oracle instantclient 11.1.0.6 with

--with-pdo-oci=shared,instantclient,/usr,11.1.0.6

I got the "Unsupported Oracle version! 11.1" error.

Reading the ext/pdo_oci/config.m4

I see 
  PDO_OCI_VERSION="`echo $PDO_OCI_IC_VERS | cut -d. -f1-2`"
which give 11.1

And  
  case $PDO_OCI_VERSION in
9.x|10.x|11.x)

Probaly  using 
  PDO_OCI_VERSION="`echo $PDO_OCI_IC_VERS | cut -d. -f1`".x

Will give better results ;)

Well and phpinfo still display "PDO Driver for OCI 8 and later" (when 8
is no mor supported).

Reproduce code:
---
-

Expected result:

-

Actual result:
--
-





-- 
Edit this bug report at http://bugs.php.net/?id=46278&edit=1



#46278 [NEW]: Unsupported Oracle version! 11.1

2008-10-12 Thread Fedora at FamilleCollet dot com
From: Fedora at FamilleCollet dot com
Operating system: Linux (Fedora 9)
PHP version:  5.2CVS-2008-10-12 (snap)
PHP Bug Type: OCI8 related
Bug description:  Unsupported Oracle version! 11.1

Description:

When trying to build against oracle instantclient 11.1.0.6 with

--with-pdo-oci=shared,instantclient,/usr,11.1.0.6

I got the "Unsupported Oracle version! 11.1" error.

Reading the ext/pdo_oci/config.m4

I see 
  PDO_OCI_VERSION="`echo $PDO_OCI_IC_VERS | cut -d. -f1-2`"
which give 11.1

And  
  case $PDO_OCI_VERSION in
9.x|10.x|11.x)

Probaly  using 
  PDO_OCI_VERSION="`echo $PDO_OCI_IC_VERS | cut -d. -f1`".x

Will give better results ;)

Well and phpinfo still display "PDO Driver for OCI 8 and later" (when 8 is
no mor supported).

Reproduce code:
---
-

Expected result:

-

Actual result:
--
-

-- 
Edit bug report at http://bugs.php.net/?id=46278&edit=1
-- 
Try a CVS snapshot (PHP 5.2): 
http://bugs.php.net/fix.php?id=46278&r=trysnapshot52
Try a CVS snapshot (PHP 5.3): 
http://bugs.php.net/fix.php?id=46278&r=trysnapshot53
Try a CVS snapshot (PHP 6.0): 
http://bugs.php.net/fix.php?id=46278&r=trysnapshot60
Fixed in CVS: http://bugs.php.net/fix.php?id=46278&r=fixedcvs
Fixed in release: 
http://bugs.php.net/fix.php?id=46278&r=alreadyfixed
Need backtrace:   http://bugs.php.net/fix.php?id=46278&r=needtrace
Need Reproduce Script:http://bugs.php.net/fix.php?id=46278&r=needscript
Try newer version:http://bugs.php.net/fix.php?id=46278&r=oldversion
Not developer issue:  http://bugs.php.net/fix.php?id=46278&r=support
Expected behavior:http://bugs.php.net/fix.php?id=46278&r=notwrong
Not enough info:  
http://bugs.php.net/fix.php?id=46278&r=notenoughinfo
Submitted twice:  
http://bugs.php.net/fix.php?id=46278&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=46278&r=globals
PHP 4 support discontinued:   http://bugs.php.net/fix.php?id=46278&r=php4
Daylight Savings: http://bugs.php.net/fix.php?id=46278&r=dst
IIS Stability:http://bugs.php.net/fix.php?id=46278&r=isapi
Install GNU Sed:  http://bugs.php.net/fix.php?id=46278&r=gnused
Floating point limitations:   http://bugs.php.net/fix.php?id=46278&r=float
No Zend Extensions:   http://bugs.php.net/fix.php?id=46278&r=nozend
MySQL Configuration Error:http://bugs.php.net/fix.php?id=46278&r=mysqlcfg



#46277 [NEW]: implicit reference is not safe to use

2008-10-12 Thread ido at niger dot co dot il
From: ido at niger dot co dot il
Operating system: Windows XP
PHP version:  5.3.0alpha2
PHP Bug Type: Scripting Engine problem
Bug description:  implicit reference is not safe to use

Description:

The example prints 9 as the value of $a , though it should be 8;
The fact the referencing $a[0] causes $a[0] to become a reference itself ,
is dangerous in cases like this where it is possible to change the value of
$a[0] though it was not originally defined as a reference.





Reproduce code:
---
function a($c){
  $c[0] = 9;
}

$a[0] = 8;

$c = &$a[0];
a($a);
echo $a[0];

Expected result:

The value of $a should be 8

Actual result:
--
The value printed is 9

-- 
Edit bug report at http://bugs.php.net/?id=46277&edit=1
-- 
Try a CVS snapshot (PHP 5.2): 
http://bugs.php.net/fix.php?id=46277&r=trysnapshot52
Try a CVS snapshot (PHP 5.3): 
http://bugs.php.net/fix.php?id=46277&r=trysnapshot53
Try a CVS snapshot (PHP 6.0): 
http://bugs.php.net/fix.php?id=46277&r=trysnapshot60
Fixed in CVS: http://bugs.php.net/fix.php?id=46277&r=fixedcvs
Fixed in release: 
http://bugs.php.net/fix.php?id=46277&r=alreadyfixed
Need backtrace:   http://bugs.php.net/fix.php?id=46277&r=needtrace
Need Reproduce Script:http://bugs.php.net/fix.php?id=46277&r=needscript
Try newer version:http://bugs.php.net/fix.php?id=46277&r=oldversion
Not developer issue:  http://bugs.php.net/fix.php?id=46277&r=support
Expected behavior:http://bugs.php.net/fix.php?id=46277&r=notwrong
Not enough info:  
http://bugs.php.net/fix.php?id=46277&r=notenoughinfo
Submitted twice:  
http://bugs.php.net/fix.php?id=46277&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=46277&r=globals
PHP 4 support discontinued:   http://bugs.php.net/fix.php?id=46277&r=php4
Daylight Savings: http://bugs.php.net/fix.php?id=46277&r=dst
IIS Stability:http://bugs.php.net/fix.php?id=46277&r=isapi
Install GNU Sed:  http://bugs.php.net/fix.php?id=46277&r=gnused
Floating point limitations:   http://bugs.php.net/fix.php?id=46277&r=float
No Zend Extensions:   http://bugs.php.net/fix.php?id=46277&r=nozend
MySQL Configuration Error:http://bugs.php.net/fix.php?id=46277&r=mysqlcfg