Hrmm, if you arent taking advantage of Oracle security and you are just running simple queries... then why invest in such an expensive database?
As far as cftransaction, it does work that way, but that logic really belongs in the model (the database) not the controller (cf). -Adam On 6/7/05, Aaron Rouse <[EMAIL PROTECTED]> wrote: > I guess we just run too simple of insert/update queries to see how > performance could ever need to be better or an issue. Although of the few > ones that effect a lot of records they are sitting in SPs, but those > statements are not what I would label "basic" either. > I thought if a cftransaction was wrapped around multiple queries and if one > query failed then the others were not commited to the database or a rollback > was done. > I understand the reasons to the security and the roles, although really how > things are setup with the data centers here, neither of them can really > apply to us(not to imply that is a good thing). > Not really following the inline function comment, probably due to lack of > education on them on my part. I know in some cfqueries here there are custom > Oracle functions called but it is a very rare thing to see done. > > On 6/7/05, Adrocknaphobia <[EMAIL PROTECTED]> wrote: > > > > 1. Performance (maybe not as much on insert, but updates an queries > > definitely faster). When running queries in Oracle, a plan is made on > > how to efficiently retrieve the data. The PL/SQL is precompiled and an > > action plan is made to optimize performance. > > > > 2. Transaction and Locking. A procedure is an implied transaction > > block that the _database_ manages. If your database supports the > > ability for transaction and locking, CF should really never be used. > > If you have multiple SQL statements to execute, when in a procedure, > > it one fails then the actions are not commited to the database. > > > > 3. Security. Security. Security. This is by far the biggest and most > > important aspect of procedures in my opinion. I can't sleep easy at > > night knowing an application's SQL statements (a roadmap diagraming > > your database) is stored in open text files on your web server (which > > is the server most commonly comprimised). > > > > Additionaly, with procedures and packages you can start to leverage > > the role based permission of your database. For instance, the only > > actions a user is allowed to perform in the database is to execute a > > certain set of methods. When the SQL is stored in CF, then the user > > must have permission to select, insert, update & delete on every table > > in your database. (Unless you want to get into the enormous task of > > specifying each table/privelage seperately) > > > > 4. Inline SQL functions. The ability to call custom functions within a > > query. > > > > These are the first 4 that benefits that come to mind, but there are > > surely more. PL/SQL is a very very very simple language. You can read > > Oracle Press PL/SQL book in a weekend and become an expert. > > > > -Adam > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:208809 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
