Sunday, 30 April 2006
blojsom on PostgreSQL
« V-Twelve | Main | PostgreSQL on OS X »Miles writes in ...
I've successfully got Blojsom 3.0 working with PostgreSQL. Why
bother, you might ask. Well, aside from me being a nutbush wide-eyed
PostgreSQL zealot, the more standardised SQL of PostgreSQL should
make it easier to port Blojsom to other database back-ends. Once we
deploy for real, we'd use PostgreSQL or Microsoft SQL Server (mainly
because we have pre-existing clusters of these, so it would be a
pretty resilient solution).
So, I need to do a few things.
1. The instructions for creating the database connection user should only have privileges for the blojsom tables.
2. The database loader bean needs to have an initialization property for allowing customized behavior per database to detect, "Do the blojsom tables exist?"
3. is a reserved keyword in PostgreSQL and ANSI SQL and so that table will be renamed to DBUser.
And finally ...
I was impressed how easy this all was. Excellent work!
Well, that's good to hear. I'll get the blojsom 3.0 wiki updated with instructions and scripts shortly.
Technorati Tags: blojsom postgresql
[Trackback URL for this entry]
Excellent news! I too am a "nutbush wide-eyed
PostgreSQL zealot."
Sidebar: Our local DB admins and developers have some prespective in the PostgreSQL vs. MySQL debate. While MySQL gets all the attention, InnoDB is now an Oracle property. They expect MySQL transaction support having to fork, be retooled completely, or MySQL to adopt the PostgreSQL transaction engine. Oracle has plateaued MySQL transaction support with the InnoDB purchase; and while not overtly hostile to Open Source, Oracle knows that MySQL is a threat in the SMB market.