In case you didn't see my suggestion for returning multiple result sets from
stored procedures:
http://www.nabble.com/Facing-problem-in-fetching-record-from-database-using-Zend-Mysqli-to16396036.html#a16628192
http://www.nabble.com/Facing-problem-in-fetching-record-from-database-using-Zend-Mysqli-to16396036.html#a16628192
I'm considering to discontinue using stored procedures - it feels like a
lonely walk in the community where everybody seems to favour building
dynamic sql at runtime. Or am I wrong - are you or anybody else still using
sps?
My previous arguments for using sps was increased performance from
precompiling and less calls to the db (returning multiple result sets in one
go). But I guess a good caching plan outweighs this, and that I can get the
benefits of more easily being able to test dynamic sql withing the
model/TDG.
One major problem with sps is that they are stored in the proc table within
the mysql database - _outside_ the database you are working with. All
clients of a mysql server share the proc table if they use sps. So of course
no hosting company will allow use of sps since access to the proc table
(=using sps) would give you access to sps of other clients. Unless you get a
virtual/dedicated server - not a thing you would like to force your
customers to have if they should move on to a new hosting company than
yourself. Or is there a workaround?
Are we waiting for a better implementation of stored procedures in MySQL, or
why aren't they used as much as in other communities (.NET, MSSQL etc.)
where they seem to be the standard?
--
View this message in context: http://www.nabble.com/Stored-procedures-caller.-tp10147171p21103919.html
Sent from the Zend DB mailing list archive at Nabble.com.
没有评论:
发表评论