php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #11187 Same as #8445: FATAL: emalloc()
Submitted: 2001-05-30 04:18 UTC Modified: 2001-06-14 12:29 UTC
From: cesare at ngi dot it Assigned:
Status: Closed Package: ODBC related
PHP Version: 4.0.5 OS: Windows 2000/SP1
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: cesare at ngi dot it
New email:
PHP Version: OS:

 

 [2001-05-30 04:18 UTC] cesare at ngi dot 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).

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-05-30 11:50 UTC] 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-06-14 12:29 UTC] kalowsky@php.net 
no user feedback.  if problem still persists, please reopen the bug with more information!
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Tue May 07 01:01:30 2024 UTC