b134b023e1
- Patch #163191 by hswong3i: removed db_num_rows() for compatibility with Oracle and DB2. Also a performance improvement.
2007-08-12 15:55:36 +00:00
a5fcb369fb
- Patch #166205 by hswong3i: improved database compatibility of db_result(). Makes it work with DB2, Oracle, etc.
2007-08-11 14:14:46 +00:00
a47d773312
- Removing some whitespace.
2007-07-23 08:05:14 +00:00
4e5d3e04ea
- Patch #159748 by pwolanin: db_fetch_array() returned different values depending on the database engine used. Make the return value consistent across all supported database backends.
2007-07-22 07:23:27 +00:00
806d0a3dee
#156910 by asimmonds: fix code indentation problems introduced with new code in this development cycle; only whitespace changes
2007-07-05 08:48:58 +00:00
2598d31ef8
#150210 by bjaspan and Frando: explicit table names for create table statements and fixing a schema referencing bug
2007-06-26 20:24:19 +00:00
27388f6655
- Patch #149176 by chx, David et al: getting rid of the sequences table, using db_last_insert_id() instead of db_next_id().
2007-06-05 12:13:23 +00:00
86e09fa401
- Patch #147692 by hswong3i: gives SQL backends more control over db_query().
2007-05-30 09:11:21 +00:00
af34a17925
- Patch #147285 by drewish: add db_rename_table().
2007-05-29 11:36:33 +00:00
3cafffe63f
- Killer patch #144765 by bjaspan, frando et al: schema API 1 hits core. Oh, behave.
2007-05-25 12:46:46 +00:00
9050e15621
- Patch #137479 by dww: added db_column_exits(). (Yay, the servers are snappy on Saturday evening.)
2007-04-21 18:08:41 +00:00
e675979091
- Patch #134493 by douggreen: getting the Drupal coding standards right in core. Woot. Woot.
2007-04-13 08:56:59 +00:00
5c99a06f9f
- Patch #85979 by RobRoy, keith.smith, fgm and webchick: improve documentation of db_next_id().
2006-12-27 22:13:56 +00:00
51c4d6aac0
- Patch #103258 by Keymone: fixed PostgreSQL bug.
2006-12-14 13:26:41 +00:00
b7094195cb
- Patch #98988 by Robert Douglass et al: db_result should return FALSE if no result was found. Consistent with PHP's mysql_result.
2006-12-04 11:06:29 +00:00
bd2527a4ed
- Patch #98059 by chx: trying to get the never-ending regex mess right.
2006-11-21 19:46:10 +00:00
1a7bac90e7
#76819 by smsimms and sammys. Move part of the sql rewriting down into the database abstraction layer and add extra rewriting needed only for Postgres.
2006-10-23 18:38:45 +00:00
e2ed7b8eef
- Patch #88705 by profix898 and sammys: made version checking work with PostgreSQL. (Critical bug)
2006-10-22 16:46:41 +00:00
845ff1c17f
- Patch #85123 by gerd: set proper HTTP headers.
2006-09-26 14:09:05 +00:00
92d0f3e602
- Patch #82137 by havran: make installer work with PostgreSQL.
2006-09-04 14:50:24 +00:00
dd4f143df6
#75002 : Install-time and run-time requirements checking + status report page
2006-09-01 08:44:53 +00:00
81938a3cdc
#76802 : Introduce placeholder magic into t()
...
See: http://drupal.org/node/64279#t-placeholders
2006-08-18 12:17:00 +00:00
885a29c4cd
- Patch #39382 by smsimms / sammys et al: make PostgreSQL password optional.
2006-08-18 08:41:49 +00:00
b14a622103
#74997 by dww, add db_table_exists()
2006-07-26 07:16:08 +00:00
1c75a210bd
- Patch #68926 by chx, jeremy, steven, eaton, webchick, amazon, neil, nedjo et al: an initial install system for Drupal core.
2006-07-13 13:14:25 +00:00
369c776c4c
SQL abstraction layer improvement.
2006-05-24 20:46:56 +00:00
ca9293b3ee
#54981 : calls to db_lock_table in bootstrap.inc do not use db_prefix
2006-04-27 20:38:49 +00:00
70aae83c8e
#58166 , fixes for typos, patch by Uwe Herrmann
2006-04-11 11:33:15 +00:00
2823cec45e
- Patch #51392 by smsimms: fixed typo in help text.
2006-02-26 19:48:43 +00:00
b1bdd4ac54
- Patch #41870 by fgm: improved debugging support.
2006-02-20 16:46:59 +00:00
ba0219e403
- Patch #21719 by rkerr: made db passwords with special characters work.
2006-01-24 08:29:33 +00:00
7914ad0f3f
- #40515 : Ensure UTF-8 character set on the database side (and include upgrade path for incorrectly set up databases)
2006-01-21 01:42:52 +00:00
3342593eac
- Patch #38889 by rkerr: db_error and db_affected_rows did not work properly in presence of multiple database connections.
2005-12-07 15:17:27 +00:00
a19acb219e
- Patch #35924 by Neil: improved the update system.
2005-12-06 09:25:22 +00:00
2d0df351d7
- Various fixes. Updated CHANGELOG.txt
2005-11-29 20:17:10 +00:00
244945365d
- Patch #10407 by Cvbge: fixed cache problems with PostgreSQL.
2005-11-27 11:52:08 +00:00
17205b6e62
#36352 : Don't prefix temporary table names after all.
...
#36658 : Make search query pgsql compatible.
2005-11-21 15:55:17 +00:00
2ad97f0277
- #36255 : Fix db_query_temporary() in pgsql
...
- Prefix temporary table names (helps on restricted hosts)
2005-11-04 13:02:51 +00:00
278e2dd309
- Add maintenance-page error screens when the php module for the dbtype is not loaded (just showed a blank screen before)
2005-10-20 21:30:50 +00:00
909d6928ac
- #28159 : Advanced search features (hello from DrupalCon)
...
Presentation about it:
http://www.acko.net/files/drupal-search-slim.pdf
2005-10-18 14:41:27 +00:00
75fad91cf5
- Patch #22911 by Cvgbe: fixed table locking in PostgreSQL. You'll have to
...
use db_lock_table() and db_unlock_tables() for your code to be compatible.
2005-08-29 19:32:55 +00:00
7b8a409675
- Patch #29385 by chx: no ?> add end of files.
2005-08-25 21:14:17 +00:00
31741b2c99
- Patch #25522 by Cvbge: _db_query() does not return FALSE in case of errors as stated in documentation.
2005-08-11 13:51:07 +00:00
897aae3e31
- #27846 : Clean up dev_query code in db_query()
2005-07-30 18:01:51 +00:00
d9d4b9bdab
- #27231 : Friendly DB error screens.
2005-07-27 01:58:43 +00:00
5c8843704c
- Patch #18213 by chx: boostrap system. Modified to work with HEAD, tidied
...
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.)
2005-06-22 20:19:58 +00:00
7dcb9086f8
- Patch #23465 by Gerhard: tiny performance improvement to db_query_range().
2005-05-23 21:14:01 +00:00
67f7d6947e
- Fixed bug #19868 : undefined variable.
2005-04-08 11:24:46 +00:00
61783651ed
- Patch #15254 : removed hardcoded 'public' schema from the PostgreSQL backend.
2005-01-07 19:18:05 +00:00
29337ad8bb
- Patch #13581 by Steven: Db_query() allows a variable amount of parameters 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.
2004-11-29 13:13:29 +00:00
Dries Buytaert
Gábor Hojtsy
Neil Drumm
Steven Wittens
Gerhard Killesreiter