People, I want to explain my DBI portability issues a bit more: Postgres is a fine product, but I would avoid using Postgres-specific functionality (like the clunky BLOB-over-oid functionality) because it breaks compatibility with every other database on the planet. Why is this important? not just because I use Perl and I want to talk to all my databases in a common dialect of SQL. It's also because, your Postgres application might one day have to be ported to a REAL database (hint! hint!) You don't want to be stuck with a tricked-up toy like Postgres when your app goes mission-critical do you? [digression:] MySQL == toy PostgreSQL == tricked-up toy Oracle = earthmover In my opinion, if your app REALLY REALLY needs enterprise-class data storage, you will stay away from PostgreSQL. Or, if you're that desperate for cash, program to a SUBset of postgres (don't use the handy-dandy but not strictly necessary fluff like objects) so that it won't be tough to implement. OTOH, you might want to check out IBM's DB2 UDB 7.24 product. A single-processor, unlimited-connection license is *only* about $2800 on Linux Intel. If you're familiar with Oracle pricing, you will recognize that IBM's pricing is virtually a steal. Any worthwhile application deserves good data storage. -- --------------------------------------------------------------------- Orlando Andico <[EMAIL PROTECTED]> POTS Phone: +63 (2) 848-2893 Mosaic Communications, Inc. GSM Mobile: +63 (917) 531-5893 I'm not suffering from insanity -- I'm enjoying every minute of it!! _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
