Agreed, in your case it may be 6 of one, half a dozen of the other.
If you were calling a stored procedure to autheticate someone, as in
CALL autheticate(username, password)
then you could conceivably later alter your entire authentication
database model without ever having to touch your applicat
At 8:49 -0500 9/8/06, Dan Buettner wrote:
Chris, I'm not aware of a way to use "ordinary" SQL (insert, update)
for this, but the use of a stored procedure would work for you. I've
not done it with MySQL (never had a need) but did things like this
extensively with Sybase.
In rough terms:
CREATE
Chris, I'm not aware of a way to use "ordinary" SQL (insert, update)
for this, but the use of a stored procedure would work for you. I've
not done it with MySQL (never had a need) but did things like this
extensively with Sybase.
In rough terms:
CREATE PROCEDURE sp_chances(IN xxx INT) RETURNS I
