#6281: SELECT COUNT(*) ... GROUP BY causes memory spike with mysqli
------------------------+---------------------------------------------------
Reporter: sdewald | Owner:
Type: Bug | Status: reopened
Priority: Medium | Milestone: 1.2.x.x
Component: MySQLi | Version: 1.2 Final
Severity: Normal | Resolution:
Keywords: | Php_version: n/a
Cake_version: |
------------------------+---------------------------------------------------
Changes (by sdewald):
* status: closed => reopened
* resolution: invalid =>
Comment:
Well, with SELECT COUNT(*) I'm really just asking for 1 row, right? I
don't think any intends for an array of millions of 1's to be loaded into
memory just to be discarded before control is returned to the user. Maybe
I'm missing something about how the internals work though.
I've attached a patch for Release: 1.2.1.8004 that might demonstrate where
I think the problem is.
--
Ticket URL: <https://trac.cakephp.org/ticket/6281#comment:3>
CakePHP : The Rapid Development Framework for PHP <https://trac.cakephp.org/>
Cake is a rapid development framework for PHP which uses commonly known design
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC.
Our primary goal is to provide a structured framework that enables PHP users at
all levels to rapidly develop robust web applications, without any loss to
flexibility.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"tickets cakephp" group.
To post to this group, send email to tickets-cakephp@googlegroups.com
To unsubscribe from this group, send email to
tickets-cakephp+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---
