ID:               20426
 User updated by:  [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
-Status:           No Feedback
+Status:           Open
 Bug Type:         MSSQL related
 Operating System: Windows 2000 Server
-PHP Version:      4.2.3
+PHP Version:      4.30
 New Comment:

OK... I've Just installed latest PHP 4.30, and the crashing 
problem is getting WORSE!

Now PHP will crash whenever I just execute "select *" from 
any table that contains two or more datetime/smalldatetime  
columns.

Again, this crashing situation disappears when I switch 
default script of Windows2000 to Japaness. But I can not 
tell my customers to do this. 

Could you nice guys just DISABLE the auto date format 
converting feature ? To us, this is not a feature; it's a 
CURSE!


Previous Comments:
------------------------------------------------------------------------

[2002-11-26 20:03:47] [EMAIL PROTECTED]

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.



------------------------------------------------------------------------

[2002-11-15 01:36:34] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip

you don't need to open new reports, you can reclassify them..(and this
belongs in mssql)


------------------------------------------------------------------------

[2002-11-15 01:36:03] [EMAIL PROTECTED]

OK, I fonud the source of this problem. It's not MSSQL 
lock/transaction problem, nor Windows 2000 Server/
Profession issue. It's due to i18n locallization settings. 
You may not be able to reproduce this cause I'm using 
TRADITINOAL CHINESE version of Windows 2000 Server and 
TRADITINOAL CHINESE version of SQL Server 2000.

Thanks for not responding. You may close this topic, cause 
this is a re-producable crash. I'm going to raise another 
topic.

------------------------------------------------------------------------

[2002-11-15 01:15:23] [EMAIL PROTECTED]

OK, I fonud the source of this problem. It's not MSSQL 
lock/transaction problem, nor Windows 2000 Server/
Profession issue. It's due to i18n locallization settings. 
You may not be able to reproduce this cause I'm using 
TRADITINOAL CHINESE version of Windows 2000 Server and 
TRADITINOAL CHINESE version of SQL Server 2000.

Thanks for not responding. You may close this topic, cause 
this is a re-producable crash. I'm going to raise another 
topic.

------------------------------------------------------------------------

[2002-11-14 21:29:32] [EMAIL PROTECTED]

The problem came back again. Service Pack did not fixed the 
problem. I'll try to reduce all unrelated code, and find 
out where the problem is.

------------------------------------------------------------------------

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

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

Reply via email to