Posted by: Administrator
on February 18, 2004 10:19 PM
I wear the same hats, DB admin for Postgres, PHP, C++ developer (with smattersing of perl and python)
All too often these days I find that I need/want a database. It really does simplify coding in the scripting language. I've reducced pages of for loops and entire C programs to a single SQL statement. (True the C program was just a report, but still...)
I would recommend people start with their favorite scripting language - I prefer PHP. Get a database - for starters, use MySQL, it is very friendly, too friendly actually. That'll get you started with databases. Then, after you're used to databases, switch to Postgres. I'd never deploy anything on MySQL aside from a simple web-site (for the constraints and cascades alone -- you have to do that in YOUR code in MySQL.) Since this is called "industrial strength databases" I'd stick with PostgreSQL, but if you're daring, skip MySQL (you won't miss anything) and jump right to PostgreSQL...
When starting out, start out right with <A HREF="http://php.weblogs.com/ADODB" TITLE="weblogs.com">ado-db</a weblogs.com> and don't look back. It'll ease transitions incase you ever have to change engines.
Learn about Linux
Download Linux
Get Linux help
This is good info
Posted by: Administrator on February 18, 2004 10:19 PMAll too often these days I find that I need/want a database. It really does simplify coding in the scripting language. I've reducced pages of for loops and entire C programs to a single SQL statement. (True the C program was just a report, but still...)
I would recommend people start with their favorite scripting language - I prefer PHP. Get a database - for starters, use MySQL, it is very friendly, too friendly actually. That'll get you started with databases. Then, after you're used to databases, switch to Postgres. I'd never deploy anything on MySQL aside from a simple web-site (for the constraints and cascades alone -- you have to do that in YOUR code in MySQL.) Since this is called "industrial strength databases" I'd stick with PostgreSQL, but if you're daring, skip MySQL (you won't miss anything) and jump right to PostgreSQL...
When starting out, start out right with <A HREF="http://php.weblogs.com/ADODB" TITLE="weblogs.com">ado-db</a weblogs.com> and don't look back. It'll ease transitions incase you ever have to change engines.
#