NTS:: Postgres vs. MySQL

I think that Postgres has a lot going for it - judging by this page on Wikipedia there's somethings which using Postgres is an advantage...

I like the idea of triggers, (must look into this), but I believe MySQL has something similar? Would be useful when you want an additive database, which is triggered by an insert on a main database:

index (is updated on INSERT of main)(keeps all information - is a "look-up database")
main (keeps only current items)

XML/Xpath sounds nice too!

Will install and see what the advantages are...

NTS:: Database structure and "flattened MaRC"

Thinking about how MaRC works, makes me think that subject (record?), property, value is not enough... or maybe I've not caught on to RDF just yet?

Column structure for a simple database (along the lines of XML and a flattened MaRC structure):

(okay, so this is not going to set the world on fire, but I think it's useable)

ROW # (autoincrement) | RECORD | LINE | ORDER | VALUE
1 | 1 | creator:surname | 001 | Smith
2 | 1 | creator:firstname | 001 | James
3 | 1 | title:entire | 001 | MySQL : Exploring database design
4 | 1 | published:date | 001 | 2004
5 | 1 | published:edition | 001 | [1st]
6 | 1 | published:date | 002 | 2006
7 | 1 | published:edition | 002 | 2nd