summaryrefslogtreecommitdiff
path: root/includes/database.pgsql.inc
Commit message (Collapse)AuthorAge
* - Patch #51392 by smsimms: fixed typo in help text.Dries Buytaert2006-02-26
|
* - Patch #41870 by fgm: improved debugging support.Dries Buytaert2006-02-20
|
* - Patch #21719 by rkerr: made db passwords with special characters work.Dries Buytaert2006-01-24
|
* - #40515: Ensure UTF-8 character set on the database side (and include ↵Steven Wittens2006-01-21
| | | | upgrade path for incorrectly set up databases)
* - Patch #38889 by rkerr: db_error and db_affected_rows did not work properly ↵Dries Buytaert2005-12-07
| | | | in presence of multiple database connections.
* - Patch #35924 by Neil: improved the update system.Dries Buytaert2005-12-06
|
* - Various fixes. Updated CHANGELOG.txtDries Buytaert2005-11-29
|
* - Patch #10407 by Cvbge: fixed cache problems with PostgreSQL.Dries Buytaert2005-11-27
|
* #36352: Don't prefix temporary table names after all.Steven Wittens2005-11-21
| | | | #36658: Make search query pgsql compatible.
* - #36255: Fix db_query_temporary() in pgsqlSteven Wittens2005-11-04
| | | | - Prefix temporary table names (helps on restricted hosts)
* - Add maintenance-page error screens when the php module for the dbtype is ↵Steven Wittens2005-10-20
| | | | not loaded (just showed a blank screen before)
* - #28159: Advanced search features (hello from DrupalCon)Steven Wittens2005-10-18
| | | | | Presentation about it: http://www.acko.net/files/drupal-search-slim.pdf
* - Patch #22911 by Cvgbe: fixed table locking in PostgreSQL. You'll have toDries Buytaert2005-08-29
| | | | use db_lock_table() and db_unlock_tables() for your code to be compatible.
* - Patch #29385 by chx: no ?> add end of files.Dries Buytaert2005-08-25
|
* - Patch #25522 by Cvbge: _db_query() does not return FALSE in case of errors ↵Dries Buytaert2005-08-11
| | | | as stated in documentation.
* - #27846: Clean up dev_query code in db_query()Steven Wittens2005-07-30
|
* - #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 #23465 by Gerhard: tiny performance improvement to db_query_range().Dries Buytaert2005-05-23
|
* - Fixed bug #19868: undefined variable.Dries Buytaert2005-04-08
|
* - Patch #15254: removed hardcoded 'public' schema from the PostgreSQL backend.Dries Buytaert2005-01-07
|
* - 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 13180 by chx: renamed check_query() to db_escape_string() and ↵Dries Buytaert2004-11-21
| | | | | | implemtented it properly per database backend. Read the manual for pg_escape_string: "Use of this function is recommended instead of addslashes()." Or read sqlite_escape_string: "addslashes() should NOT be used to quote your strings for SQLite queries; it will lead to strange results when retrieving your data."
* - Patch #10945 by Adrian: more PostgreSQL fixes/updates.Dries Buytaert2004-09-20
|
* - 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).
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-23 18:44:22 +0000