Feature #23374
Add support for prepared queries
| Status: | Resolved | Start date: | 2010-08-14 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Xavier Perseguers | % Done: | 0% |
|
| Category: | Database API | Spent time: | - | |
| Target version: | - | |||
| PHP Version: | 5.2 | Sprint Focus: | ||
| Complexity: |
Description
Prepared queries would help take better advantage of advanced usage of underlying DBMS and would allow DBAL to be much more efficient by allowing parsed and rewritten queries to be cached.
(issue imported from #M15457)
15457_dbal.diff
(12.5 kB)
15457_core.diff
(20.3 kB)
15457_core_v2.diff
(20.6 kB)
15457_dbal_v2.diff
(13.6 kB)
15457_dbal_v3.diff
(15 kB)
Related issues
History
#1 Updated by Xavier Perseguers almost 5 years ago
v2 implements the TODO of first version:
Find a way to already compile the query into a string while preserving the information
where each parameter appears. This will prevent compiling and compiling again the
query in method stmt_execute() and will allow caching of the query into Memcached and
as such completely bypass the parsing of the already seen before SELECT query.
This will allow #21614 to be fixed.
#2 Updated by Xavier Perseguers almost 5 years ago
dbal_v3 fixes issues when really using DBAL (local unit tested with Oracle).
#3 Updated by Xavier Perseguers almost 5 years ago
Committed to:
- Core trunk (rev. 8612)
- DBAL trunk (rev. 36983)