summaryrefslogtreecommitdiff
path: root/includes/database.inc
Commit message (Collapse)AuthorAge
* - Removing whitespace.Dries Buytaert2007-08-30
|
* #168812 by webchick and pwolanin: in case we have a database error, trace it ↵Gábor Hojtsy2007-08-29
| | | | back to the original database function call, so we can provide a more accurate error message for DB errors
* #157682 by bjaspan, chx and JirkaRybka: update.php for Drupal 6, to allow ↵Gábor Hojtsy2007-08-26
| | | | near flowless updates
* #164759 by oadaeh: adding missing phpdoc @code tagGábor Hojtsy2007-08-06
|
* #158133 by killes: do not break HAVING SQL constructs in SQL rewritesGábor Hojtsy2007-07-12
|
* - Patch #155986 by Uwe: fixed typos.Dries Buytaert2007-07-02
|
* #155282 by Jose A Reyero: apply db_rewrite_sql() to the block listing query ↵Gábor Hojtsy2007-07-01
| | | | to allow for multilingual blocks
* #150210 by bjaspan and Frando: explicit table names for create table ↵Gábor Hojtsy2007-06-26
| | | | statements and fixing a schema referencing bug
* - Patch #147692 by hswong3i: gives SQL backends more control over db_query().Dries Buytaert2007-05-30
|
* - Killer patch #144765 by bjaspan, frando et al: schema API 1 hits core. ↵Dries Buytaert2007-05-25
| | | | Oh, behave.
* - Patch #99011 by merlinofchaos: remove sites/default/settings.php and ship ↵Dries Buytaert2007-05-08
| | | | with sites/default/default.settings.php.
* - Patch #134493 by douggreen: getting the Drupal coding standards right in ↵Dries Buytaert2007-04-13
| | | | core. Woot. Woot.
* #130991: Custom menu items, part 1Steven Wittens2007-04-06
|
* #126867: Reverting bad db_prefix_tables change.Steven Wittens2007-03-15
|
* - Patch #126867 by dmitrig01: fixed caching in presence of database prefixes.Dries Buytaert2007-03-14
|
* - Patch #32833 by fgm: fixed documentation error.Dries Buytaert2007-02-27
|
* - Patch #106370 by naquah and chx: fixed query rewriting in presence of ↵Dries Buytaert2007-01-03
| | | | OR-clause.
* #102611: Document database regexp (webchick)Steven Wittens2006-12-11
|
* #76819 by smsimms and sammys. Move part of the sql rewriting down into the ↵Neil Drumm2006-10-23
| | | | database abstraction layer and add extra rewriting needed only for Postgres.
* #42476 by Bèr Kessels. db_queryd() belongs in devel module.Neil Drumm2006-09-08
|
* #79904 by chx. More strict db_rewrite_sql() regexp.Neil Drumm2006-08-24
|
* - Patch #72204 by nedjo: upper-cased all TRUE/FALSE/NULL constants.Dries Buytaert2006-07-05
|
* #54981: calls to db_lock_table in bootstrap.inc do not use db_prefixSteven Wittens2006-04-27
|
* #16542, add db rewriting for menus, patch by chxGerhard Killesreiter2006-04-07
| | | | fixes 57406 too
* #42000, misssing underscore, found by rumpGerhard Killesreiter2006-03-26
|
* #42000, docs update, by meGerhard Killesreiter2006-03-26
|
* #42000, Watchdog can't log errors when using db_set_active(non-default), ↵Gerhard Killesreiter2006-03-26
| | | | patch by Chris Johnson and myself
* - Patch #51850 by chx, webchick et al: fixed various problems with ↵Dries Buytaert2006-03-08
| | | | db_rewrite_sql, made db_rewrite_sql slightly more robust.
* - Patch #41644 by chx: critical bug: db_rewrite_sql had a bad regex.Dries Buytaert2006-01-08
|
* - Patch #40631 by Chris Johnson: is_array() slower than isset() or empty().Dries Buytaert2005-12-14
|
* - Patch #39257 by merlinofchaos: node_access rewrite breaks with FROM_UNIXTIME.Dries Buytaert2005-11-29
|
* - Patch #10407 by Cvbge: fixed cache problems with PostgreSQL.Dries Buytaert2005-11-27
|
* - Patch #29910 by m3avrck, nsk, Thomas et al: added a mysqli database ↵Dries Buytaert2005-09-12
| | | | | | backend for use with PHP5 and MySQL 4.1 and above. NOTE: I don't have MySQL 4.1 setup at the moment so I could _not_ test this patch. Luckily, various people reported that it works.
* - Patch #30122 by m3verick: changed include_once()'s to include "./$file"Dries Buytaert2005-09-08
| | | | for performance's sake.
* - Patch #29385 by chx: no ?> add end of files.Dries Buytaert2005-08-25
|
* - #27231: Friendly DB error screens.Steven Wittens2005-07-27
|
* - Patch #18213 by chx: boostrap system. Modified to work with HEAD, tidiedDries Buytaert2005-06-22
| | | | | | | up the documentation a little. chx: can you double-check whether the global $conf variable is secure? (That is, make sure it can't be send using the URL or something.)
* - Patch #19609 by Daniel: fix problem with database prefixingDries Buytaert2005-04-08
|
* - Fixing broken search after sql rewrite patchesSteven Wittens2005-02-19
| | | | - Minor code style fixes.
* - #16111: bad quotes in db_rewrite_sqlSteven Wittens2005-02-05
|
* - Patch #16111 by chx: fixed some bugs in the db_rewrite_sql() code.Dries Buytaert2005-01-31
|
* - Patch #16111 by chx: PHPdoc/documentation improvements.Dries Buytaert2005-01-30
|
* - Patch #16111 by chx: generalized node_rewrite_query to db_rewrite_query.Dries Buytaert2005-01-29
|
* - Patch #13020 by chx: let Drupal handle multiple database layers.Dries Buytaert2004-12-30
| | | | - Removed the PEAR database backend. It's no longer being used/maintained.
* - Patch #13581 by Steven: Db_query() allows a variable amount of parameters ↵Dries Buytaert2004-11-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | so you can pass the query arguments in. There is however an alternative syntax: instead of passing the query arguments as function arguments, you can also pass a single array with the query arguments in it. For example the following two statements are equivalent: db_query($query, $a, $b, $c); db_query($query, array($a, $b, $c)); This usage is particularly interesting when the query is constructed dynamically, and the amount of arguments to pass varies. In that case we use the second method to avoid using call_user_func_array(). This behaviour is not documented explicitly, but it is used in several places. However, db_query_range() and pager_query() do not support this syntax properly, which means there are several pieces of code which still revert to the ugly call_user_func_array() call. This patch updates db_query_range() and pager_query() so they support the array-passing method. I also added documentation about this method to each of the db functions. I also cleaned up the code for db_query (it was weird and hard to understand) and moved db_query() and db_queryd() from database.xxxxx.inc to database.inc: it was the same between both mysql and pgsql, as it doesn't do anything database specific. It just prefixes the tables and inserts the arguments. The actual db query is performed in _db_query(), which is still in database.xxxxx.inc. Finally, I updated several places with the new syntax, and the code is a lot cleaner. For example: - array_unshift($params, "SELECT u.* FROM {users} u WHERE $query u.status < 3"); - $params[] = 0; - $params[] = 1; - $result = call_user_func_array('db_query_range', $params); + $result = db_query_range("SELECT u.* FROM {users} u WHERE $query u.status < 3", $params, 0, 1); and - return call_user_func_array('db_query_range', array_merge(array($query), $args, array((int)$pager_from_array[$element], (int)$limit))); + return db_query_range($query, $args, (int)$pager_from_array[$element], (int)$limit); I've tested it on mysql. I didn't alter the actual db behaviour, so pgsql should be okay too. This patch is important because many people avoid the call_user_func_array() method and put data directly into the db query. This is very, very bad because the database prefix will be applied to it, and strip out braces. It's also generally bad form as you have to call check_query() yourself. With the new, documented syntax, there is no more excuse to put data directly in the query.
* - Patch #10663 by JonBob: documentation improvements: fixed some typos and ↵Dries Buytaert2004-09-09
| | | | improved consistency to the use of Doxygen/api.module commands in the comments.
* - Patch #10622 by Adrian: fixes various PostgreSQL related problems.Dries Buytaert2004-09-08
| | | | | | | | | | | | | 1) Menu problems with Postgres (this is a highly critical 1 line fix) 2) Archive module fails with Postgres 3) Postgres setup problems - changes to database.pgsql (although i made these changes myself before finding this patch) 4) Book module fails with Postgres 5) Postgres problems following creation of a new type of user - which is actually about a taxonomy.module bug. 6) Creating accregator_item_table in PostgreSQL 7) Postgres - Polls not displayed on Poll Page 8) Blog module has sql errors with postgres This should not affect MySQL users (hopefully).
* - Patch #9287 by JonBob: made the code style in the three database include ↵Dries Buytaert2004-07-14
| | | | files consistent with Drupal standards, and adds a wealth of Doxygen-style comments to aid developers in writing solid database access code using the API.
* - Patch #7575 by ax: not in global scope, making updates fail.Dries Buytaert2004-05-06
|
* - Patch by Adrian: added support for multiple database connections.Dries Buytaert2004-04-30
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-07 03:08:05 +0000