Anonymous | Login | Signup for a new account | 2024-04-29 01:39 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Dependency Graph | [ View Issue ] [ Relation Graph ] [ Vertical ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0001147 | [In-Portal CMS] Database | feature request | N/A | 2011-10-17 08:31 | 2012-07-25 05:32 |
Reporter | alex | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | fixed | ||
Status | closed | ||||
Summary | 0001147: Methods for processing large data amounts from database | ||||
Description |
In-Portal nice $this->Application->Conn->Query method, that accepts SQL and returns an array of data to used right away. This proved very useful for small sets of data. However, when you need to process 2000 or more records, then this method will eat up a lot of memory while transforming sql result into PHP array. Attached methods contains kDBConnection::QueryRaw and kDBConnection::GetNextRow methods, that basically does the same what mysql_query and mysql_fetch_assoc methods. Also kDBConnection::Destroy method was changed to accept incoming recordset resource, that needs to be destroyed. Here is usage example: $rs = $this->Conn->QueryRaw($sql); while ( $row = $this->Conn->GetNextRow($rs) ) { echo $row['userid']; echo $row['fullname']; echo $row['userstatus']; } $this->Conn->Destroy($rs); |
||||
Additional Information |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |