Project

General

Profile

Actions
Copy link

Feature #21025

closed

Performance improvement for queries that expect just a single result row

Added by Jo Hasenau about 15 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Ernesto Baschny
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2009-09-10
Due date:
% Done:

0%

Estimated time:
PHP Version:
4.3
Tags:
Complexity:
Sprint Focus:

Description

I would like to introduce a new function exec_SELECTgetSingleRow() to prevent exec_SELECTgetRows() being used for queries that definitely expect only one row to be returned.

Just like exec_SELECTgetRows() it will contain all necessary function calls to execute the query, get the result row, free the result and return the data.

To avoid any additional function calls IMHO it should not be a variant of exec_SELECTgetRows() but another function.

Additionally it should be used in all places within the core, that are using exec_SELECTgetRows() but expecting single result rows only, to speed up the overall performance of the system. (An indicator could be LIMIT the rest can be recognized by checking the context)

Remaining question: If I create a patch should this contain all these changes at once or should this be done in different patches with their own bugtracker entry?

(issue imported from #M11916)

Files

Download all files
exec_SELECTgetSingleRow.diff (20.6 KB) exec_SELECTgetSingleRow.diff Administrator Admin, 2009-09-15 13:32
11916.diff (1.45 KB) 11916.diff Administrator Admin, 2010-11-13 18:56
11916_v4.diff (1.92 KB) 11916_v4.diff Administrator Admin, 2010-11-14 16:32
Actions
Copy link

Also available in: Atom PDF