Daniel Convissor wrote:
Whether it's in the database or in PHP, changing DBMS'es requires
recoding some aspects of the project. So put things where they best
belong. In the case you're proposing, a stored procedure is the right
way to go.
I would add that stored procedures also allow you support a mix of
different application languages sharing the same procs. For instance,
some shops mandate PHP on the web side and Perl (etc.) for the async
scripts.
_______________________________________________
New York PHP Users Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org/Show-Participation
