1. 03 Jan, 2007 1 commit
  2. 11 Dec, 2006 1 commit
  3. 23 Oct, 2006 1 commit
  4. 08 Sep, 2006 1 commit
  5. 24 Aug, 2006 1 commit
  6. 05 Jul, 2006 1 commit
  7. 27 Apr, 2006 1 commit
  8. 07 Apr, 2006 1 commit
  9. 26 Mar, 2006 3 commits
  10. 08 Mar, 2006 1 commit
  11. 08 Jan, 2006 1 commit
  12. 14 Dec, 2005 1 commit
  13. 29 Nov, 2005 1 commit
  14. 27 Nov, 2005 1 commit
  15. 12 Sep, 2005 1 commit
  16. 08 Sep, 2005 1 commit
  17. 25 Aug, 2005 1 commit
  18. 27 Jul, 2005 1 commit
  19. 22 Jun, 2005 1 commit
  20. 08 Apr, 2005 1 commit
  21. 19 Feb, 2005 1 commit
  22. 05 Feb, 2005 1 commit
  23. 31 Jan, 2005 1 commit
  24. 30 Jan, 2005 1 commit
  25. 29 Jan, 2005 1 commit
  26. 30 Dec, 2004 1 commit
    • Dries Buytaert's avatar
      · 828be2ad
      Dries Buytaert authored
      - Patch #13020 by chx: let Drupal handle multiple database layers.
      
      - Removed the PEAR database backend.  It's no longer being used/maintained.
      828be2ad
  27. 29 Nov, 2004 1 commit
    • Dries Buytaert's avatar
      - Patch #13581 by Steven: Db_query() allows a variable amount of parameters so... · 29337ad8
      Dries Buytaert authored
      - 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.
      29337ad8
  28. 09 Sep, 2004 1 commit
    • Dries Buytaert's avatar
      · b84b6e42
      Dries Buytaert authored
      - Patch #10663 by JonBob: documentation improvements: fixed some typos and improved consistency to the use of Doxygen/api.module commands in the comments.
      b84b6e42
  29. 08 Sep, 2004 1 commit
    • Dries Buytaert's avatar
      · 7b716e8e
      Dries Buytaert authored
      - Patch #10622 by Adrian: fixes various PostgreSQL related problems.
      
        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).
      7b716e8e
  30. 14 Jul, 2004 1 commit
    • Dries Buytaert's avatar
      · 63a327db
      Dries Buytaert authored
      - Patch #9287 by JonBob: made the code style in the three database include 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.
      63a327db
  31. 06 May, 2004 1 commit
  32. 30 Apr, 2004 1 commit
    • Dries Buytaert's avatar
      · e4d45aae
      Dries Buytaert authored
      - Patch by Adrian: added support for multiple database connections.
      e4d45aae
  33. 01 Oct, 2003 1 commit
    • Dries Buytaert's avatar
      · fa2581ed
      Dries Buytaert authored
      - Modifies path.module to get rid of pgsql reserved word.  Patch by Adrian.
      
      - Updates database.pgsql and database.mysql to work with current cvs. Patch
        by Adrian.
      
      - Updates update.php to be able to update postgres from 4.2 to current.
        Patch by Adrian.
      
      - Small fixes by me.
      fa2581ed
  34. 26 Aug, 2003 1 commit
    • Dries Buytaert's avatar
      · b7727227
      Dries Buytaert authored
      - Committed Moshe's selective table rewriting patch.  Makes it possible to
        share some database tables but not others.
      b7727227
  35. 10 Jul, 2003 1 commit
    • Dries Buytaert's avatar
      · 337b3c9d
      Dries Buytaert authored
      - Committed a slightly modified version of Slavica's table prefix patch.
      337b3c9d
  36. 05 Nov, 2001 1 commit
    • Dries Buytaert's avatar
      · db47bac3
      Dries Buytaert authored
      - node.module:
      
         + Changed node_form() to use good ol' tables instead of div/CSS-tags.
      
         + Revised the "revision API": I think we have both an easy and powerful
           API now that should make everyone happy.
      
         + Improved the usability of the rollback functionality a bit.
      
         + Removed the "view node" link from the "node overview" page in the
           admin section and added a "delete node" link instead.
      
         + Added a few missing translations; there might be missing more
           translations though.
      
      - book.module:
      
         + Made the book module use the "revision API" instead of having it poke
           and use the innards and underlying details of the revision system.
      
      - queue.module:
      
         + Made the queue module use the improved revision number.
      
      - module.inc:
         + Applied Moshe's patch: added more arguments to module_invoke()
      
      - mail-to-sql.pl:
         + Added support for more header fields and for folded fields
      
      Notes:
      
      - no database updates required
      db47bac3
  37. 31 Oct, 2001 1 commit
    • Dries Buytaert's avatar
      · 7c181aba
      Dries Buytaert authored
      - Made some improvements/updates to the database abstraction layer.
      7c181aba
  38. 20 Oct, 2001 1 commit