- 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.

- Committed Moshe's selective table rewriting patch.  Makes it possible to
  share some database tables but not others.

- Committed a slightly modified version of Slavica's table prefix patch.

- 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

- Made some improvements/updates to the database abstraction layer.

  easier. Also changed the <? tag to <?php in some cases.

- Small improvement to db_query() to make debuging queries a bit more easy.

- added sequence tables

- fixed bug in node_page()

- fixed bug in db_result()

- fixed rss glitch

- PEAR-ification of Drupal by claw: you can now host Drupal on a wide
  range of databases including MySQL, PostgreSQL, MSSQL, and others.

  For additional information and an 'how to upgrade', check the mails
  sent to the mailing list.

- Improved db_fetch_array() to return an associative array only:
  passing around arrays should be less expensive.

- Redid settings.module and even renamed it to conf.module.
    * Settings are now grouped in basic categories like "system
      settings", "module settings" and "filters".
  * Added new settings to make Drupal easier to configure and
  to make some aspects like the watchdog scale better.

- Renamed includes/settings.php to includes/conf.php.

- Added filter support to conf.module and introduced filter hooks so
  modules can implement and export new filters.  Example filters are
  an HTML filter (implemented), a profanity filter, an url converter,
  ASCII smileys to images filter and so on ...

- Reworked the check_* functions: user contributed content/input is
  only verified and filtered once in its lifespan.

NOTES

- Altough this is a large commit, no database changes are required.

- added new variable: theme_footer which can be used to provide a
  footer message like a copyright notice. Themes should use this!
- small improvement to example theme
- added theme_footer to theme marvin
- small improvement to database.inc

Last nights updates (under construction):
  - added _type() hook so each module can return the content types he/she
    implements

- improved rating module: it now shows some basic statistics :-)
- updated database files
- removed affialiate-site and drupal-site module: maintain them
  by hand through a box for now will you.

would be to support more databases :-)

- applied David Norman's patch to turn all <?'s into fully qualified
  <?php's.

- fixed small translation glitch in format_interval
- added a couple of missing t() functions
- improved the comments module, fixed the score problem Jeroen
  reported earlier -> it's slicker but I hope it won't break anything

- removed redundant spaces

A batch of patches:

  - configuration:
    + renamed $db_name to $db_user
    + renamed $db_base to $db_name
  - fixed small diary glitch
  - fixed initial-comment-score problem
  - fixed comment rating bug: improved the API and updated the
    themes
  - removed some tabs from Steven ;)
  - fixed backend warnings and improved robustness
    I'm not happy yet with the headline grabber - it generates
    too many SQL errors.
  - some small cosmetic changes in comment.module
  - fixed minor glitch in format_interval()

- here a bunch of changes to make "drupal" (for now) work with PHP 4.0.4
- tidied up some of the code and mainly working on the documentation

- large batch of updates

- changed quite a lot of things around, including small bug fixes (nothing)
  critical and module support.  The faq.php will - for instance - become a
  module

Another batch with a lot of internal updates, yet no visual changes to the
site:

- watchdog (rewrite):
   + the collected information provides more details and insights
     for post-mortem research
   + input limitation
- database abstraction layer:
   + mysql errors are now verbose and is no longer displayed in a
     browser - fixes a possible security risk
- admin.php:
   + updated watchdog page
   + fixed security flaw
- diary.php:
   + fixed nl2br problem
- themes:
   + fixed comment bug in all 3 themes.
- misc:
   + renamed some global variables for sake of consistency:
      $sitename  -->  $site_name
      $siteurl   -->  $site_url
   + added input check where (a) exploitable and (b) possible
   + added input size check
   + various small improvements
   + fixed various typoes

... and much, much more in fact.

A big, fat commit with a shitload of internal changes.  Not that much
visual changes:

- removed redundant files user.class.php, calendar.class.php
  and backend.class.php.
- converted *all* mysql queries to queries supported by the
  database abstraction layer.
- expanded the watchdog to record more information on what
  actually happened.
- bugfix: anonymous readers where not able to view comments.
- bugfix: anonymous readers could gain read-only access to
  the submission queue.
- bugfix: invalid includes in backend.php
- bugfix: invalid use of '$user->block'

and last but not least:

- redid 50% of the user account system

structure changes, some sections are expanded.  Take a look at the source
code or ask me to elaborate on certain issues/topics.

- Added a basic implementation of comment moderation
- Updated and renamed my 2 themes: I removed redundant boxes and tried to
  work towards simplicity.
- Disabled the other themes as they are broken (I gave you sufficent time
  to update them).
- Removed redundant files.
- Added security checks with regard to the usage of HTML tags.

* _Major_ update of the comments and moderation system: it's a lot more
  stream-lined and more compact.  There are a few parts I like to optimize
  prior to heading towards comment moderation.

  Please test, report bugs and update the footer()-part of your themes a
  bit (see my theme)!!!


-- Dries

* Commited a *temporary* version of the new comment system: I have been
  working on it for about 4 a 5 hours today and I considered it would be
  smart (backup- or crash-wise) to commit what I have made so far.  I'm
  aware of a few bugs and I'll keep workin on it:
    - removing bugs
    - clean up the code to make it very streamlined
    - improve error checking
  Once we got a stable comment system, I'll add moderation.  But right
  now I want to sort out the major problems.
* I made my theme the default theme until the other themes are updated.
* Expanded the database abstraction layer with more goodies.

* Integrated the database abstraction layer into the account pages.  One
  reason for doing so is because the database abstraction layer provides
  build-in error checking and a debug mode for easy development.

Updates:
 * Streamlined the database abstraction layer a bit (it's not much yet) and
   integrated it in most of the functions of `functions.inc'.

* databases.inc is a new file that will serve as a database abstraction
  layer.  My new files already take advantage of the abstraction layer
  though no attempt is made to port the existing files: this is sheduled
  for a future v0.40 release (see http://beta.drop.org/docs/roadmap.php).
  Anyway, with the abstraction layer it should be theoretically possible
  to run drop on top of every database, even on top of a home-brewed
  file-based system.  *wink-to-UnConeD* ;-)