und ich versuche eher zu vermeiden, MySQL-only Lösungen einzusetzen.

Für diesen Satz könnte ich dir mal wieder die Füße küssen! Endlich mal wieder ein vernünftiger PHP-Coder, für den der Tellerrand nicht bei MySQL aufhört.

Take a look at the FAQ: http://www.s9y.org/11.html

Perhaps a definition of your "it doesn't work" could be helpful.

Count me in on that one. Maybe Trackbacks are moderated in this case?

After mulling over "how to do this" for a while, I simply ask you: How?

Just install the "extended categories"-Plugin. S9Y 0.9beta3 is pretty stable, and it looks as if the last bugs will be fixed soon.

Great. One more bug fixed.

But this does work! Remember that if you entered the password once, you are authenticated for those categories/entries until you close your browser!

Damn. Sorry, I forgot that this isn't S)Y's own authentication working there.

While playing around a little with password-protected categories, I found something kinda strange: I set up one password-protected category that may only show one entry on the frontpage. Whenever a password is set for that category, I can't see the entry within "Edit entries" wihtin the ba...

Why don't you just password-protect it?

Just plain-ol' Postgres. It'd be just perfect if you could make that possible.

Whee, great stuff! I'd love to see that one public...although I fear it's kinda MySQL-centric.

Playing around with another testblog (S9Y 0.9beta3), I found another Postgres-related "error" within plugin_internal.inc.php. When the categories-sidebar-plugin was activated, PHP throws out an error within a "GROUP BY"-statement Warning: pg_query(): Query failed: ERROR: column &...

Three Bugs in 5 Hours. Uhuh. Don't say this to heise.de

Why? Nobody beats Microsoft in this case...

Thanks Garvin for your great work on S9Y.

OK, I found your explanation about referrer-handling. Read it once, read it twice, (think I) understood, but this also doesn't help me in this case: "legal" referrers are only put into serendipity_suppress, not further processing takes place. In this case, I'm still wondering how to debug ...

COLUMN ist optional:

http://www.postgresql.org/docs/7.4/static/sql-altertable.html wrote:Notes

The key word COLUMN is noise and can be omitted.

Kann es sein, dass postgreSQL kein MULTI-Alter Table unterstützt? Ich lasse mich da gerne eines Besseren belehren, aber so scheint's zu sein: ALTER TABLE serendipity_staticpages ADD test1 int4 ADD test2 smallint; ERROR: syntax error at or near "ADD" at character 52 Laut Doku geht das wohl...