[KLUG Members] PHP and MYSQL

[bill]

For someone -starting off- to learn php & mysql, I disagree about using ODBC.  Learn the easiest, fastest way first, which is php & mysql.  Not everyone is going to end up using Oracle.

Those who are fond of Postgres and Oracle often assume everyone will migrate to them eventually, and thereforer recommend setting up to do so.  But that's a lot of unnecessary overhead if the project never goes there, and
overly prudent unless the project calls for it.  Unless there is a known, compelling reason to do otherwise (in the project, not the fears of naysayers), I'd recommend doing what works easy and well: php & mysql.

Not everybody needs to drive a Volvo.

kind regards,

bill

Adam Williams wrote:

> >I'd strongly recommend -not- starting projects off tieing them to a specific DB.  You'll probably get far more done in the long run if you start looking at something like ADOdb for PHP rather than mysql specific calls.
> >Besides, then you can port it to PostgreSQL easier later. :)
>
> Or use PHP's unixODBC support.  Then you don't have to depend on the
> maintainer of one of the zillion data base abstraction classes to not
> having a stroke while walking to get the morning paper.  Push the
> abstraction straight of the programming environment (ODBC),  and ODBC
> isn't going to "go away" and someone isn't going to rewrite the API
> underneath you.
>
> Clearly defined tiers of functionality is a very good long-term
> development strategy.
>
> Then you can 'port' it to Oracle later.
>
> _______________________________________________
> Members mailing list
> Members@kalamazoolinux.org
>