Bug #11187 Updated: Same as #8445: FATAL: emalloc()
| From: | kalowsky@php.net | Date: | Thu, 14 Jun 2001 16:29:42 +0000 |
| Subject: | Bug #11187 Updated: Same as #8445: FATAL: emalloc() | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-57076@lists.php.net to get a copy of this message | ||
ID: 11187
Updated by: kalowsky
Reported By: cesare@ngi.it
Old-Status: Feedback
Status: Closed
Bug Type: ODBC related
Operating system:
PHP Version: 4.0.5
Assigned To:
Comments:
no user feedback. if problem still persists, please reopen the bug with more information!
Previous Comments:
---------------------------------------------------------------------------
[2001-05-30 11:50:21] kalowsky@php.net
you need to give me more detail as i cannot reproduce this in ANY sample script. although i'm
only on win98SE using Apache Win32.
---------------------------------------------------------------------------
[2001-05-30 04:18:26] cesare@ngi.it
It is simply the same as the closed bug #8445 (similar script):
SELECT * FROM table;
Result:
FATAL: emalloc(): Unable to allocate 1073741824 bytes
My resultset is NOT 1GB, it's far less than that.
I noticed that it occurs only if the SELECT is requested on
tables that have NOT NULL fields which are empty (the NOT
NULL field was added in a second time, so all rows have that
field empty).
Also, if I request only some fields (not *), the query is
OK. Seems a combination of a "feature" of SQL server 7 and a
misinterpretation of the data by PHP (I suppose).
---------------------------------------------------------------------------
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=11187&edit=2