> why aren't they used as much as in other communities (.NET, MSSQL etc.)
> where they seem to be the standard?
There are two paradigms for using sql for data access with applications:
dynamic sql and stored procedures. Both are very much standards, it just so
happens the one you might settle on depends A LOT on what kind of team you
run. Generally speaking, in order to use stored procedures, you need to
have a "database programmer" on your team. This would be someone who is
capable of both writing and testing the SP's that an application might
require.
In shops that generally use .net and mssql, you see teams that have both
Database Administrators as well as Database Developers IN ADDITION to your
application developers. In situations like these, it makes a lot of sense
to use stored procedures b/c you have the resources available to maintain
that solutions.
In web shops that are only web developer centric, maintenance of this type
of solution (SP's), makes the alternative (dynamic sql) much more appealing.
Also keep in mind, even when talking about SP's, a simple crud action for a
table AT LEAST requires 4+ stored procedures: (insert, update, delete,
select by id, ....).
Its not that its "standard", its about choosing a paradigm that you can
maintain long term ;)
-ralph
--
Ralph Schindler
Software Engineer | ralph.schindler@zend.com
Zend Framework | http://framework.zend.com/
没有评论:
发表评论