> I don't see the value of using SPs for such basic operations, > to be honest. Maybe on an insert so as to return the PK, but > in our situation, we specify the PK ourselves (createUUID()), > so we've no need for this. > > But if you're just doing a SELECT statement from one table... > Why use a SP (serious question... Like I've said before...
There are several reasons why you might want to use SPs for all of your data access if possible. First, you can more effectively secure data access if you use SPs exclusively and don't allow any passthrough SQL. Second, you may see performance benefits even with simple operations on certain platforms. Third, you will achieve a better separation of data access logic, and the ability to reuse that logic from other applications if desired. Of course, there are some disadvantages to using SPs, but I usually find them outweighed by the advantages. > I'm a SP bunny, so might be missing something). I'm not sure what an SP bunny is, actually. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ phone: 202-797-5496 fax: 202-797-5444 ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
