remove new line characters at the end of the sql_generator class files

What is wrong with these single newlines? We have them all over the place. It would be imho problem only if there were two newline chars after the ?>, right?

If you have any character outside php tags and php's output buffering if off, then sending http headers will not work.

added support for loading pdo subclasses. it could be merge with the if from adodb.

One unix newline is fine after the ?>, no need to remove it - the proof is moodle code itself because it has it in many files.
see: http://us.php.net/manual/en/faq.using.php#faq.using.newlines

I have changed the datalib code to accept any $CFG->dblibrary

• fixed dblibrary (instead of library)
• put code for storing db params into moodle_database contructor; subclasses can call it later
• change TRUNCATE TABLE to DELETE FROM (which is not mysql specific)

sorry about the tabs.

1/ Fixed the cfg->library typo - thanks!

2/ I was thinking about refactoring of connect() and config saving function, in the end we might not need to store
$cfg->dbhost = $this->dbhost;
$cfg->dbname = $this->dbname;
$cfg->dbuser = $this->dbuser;
$cfg->dbpass = $this->dbpass;
at all

3/ TRUNCATE is optimal there, just override it in sqlite driver

2. caching that information may prove useful and doesn't take that much space. however, we could move it to pdo_moodle_database, as adodb_moodle_database does it's own caching.
3. truncate may be optimal, but is it standard SQL? I think moodle_database should be as general as posible and subclasses should handle particularities. however, if you decide to use delete, there's an error there. I'll provide a new patch later on.

2. I am going to rewrite this, the caching is not needed at all there because we do not support database reconnecting
3. this is not about standards, this is about databases we officially support - all of them allow TRUNCATE; in fact we never care about standards as long as it works in all supported databases
If you removed it from moodle_database we would have to add it into all drivers except sqlite, that would be far bellow optional.

2. caching this information may be used for other purposes: find out the curently used database to show that information to admins or create a new connection with same parameters (or just a part of them).
X. if you have time, check http://tracker.moodle.org/secure/ManageAttachments.jspa?id=26733
Thanks.

Columns cache should be cleared after ddl statements.

this should be all in cvs I hope, closing for now
big thanks!!