ads' corner

Why you should use schemata instead of multiple databases

Just a week ago I had a discussion with a MySQL fellow about pro and contra for schemata (schema.table as example in PostgreSQL) or use of multiple databases (database.table in MySQL).

Today I found this article.

And of course this is another big argument against the possibility of accessing two or more databases in one query statement.


Rasmus Lerdorf is praising PHP ...

Rasmus Lerdorf, the creator of PHP, tells us (here), that the web is broken and “we” had damaged it. But there would be PHP, which can fix all the issues. Ok, let’s see what Rasmus has to tell us.


PHP does not need Transactions

Just stumbled about a curiosity: there are 82 functions in the current PostgreSQL part of PHP. Functions like pg_select(), which takes from you the burden of writing a SELECT ... FROM tablename or pg_delete(), pg_insert() and pg_update() which all does, what do you expect: SELECT, DELETE, INSERT or UPDATE, and do the error checking. There are even 7 different functions for getting your results back into PHP.

But there is no function for starting, committing or rolling back a transaction. It seems, the message about the usefulness of transaction has yet not reached the PHP developers. Not that I’m surprised, the standard PHP/MySQL user seems to have no need for transactions …


frisch am Morgen

Da öffnet man nichtsahnend eine Newsgroup und schon wird einem der Tag verschönt:


Backups ... properly

Today I found this little script which does backups on a server:


MySQL and Foreign Keys

If you ever try to use Foreign Keys in MySQL (of course, only the InnoDB engine supports this), don’t forget, that the columns in both tables must have exactly the same definition.