CFQUERY will not return back a new identity either, well depending on the database chosen it will not without a second cfquery. Just curious, not implying anything wrong with it one bit, but what are your reasonings for using almost all SPs for your DB work? Also curious the reasons for that since different people seem to give completely different reasons for it.
On 5/12/05, Glenn Saunders <[EMAIL PROTECTED]> wrote: > > > Well, for one thing, because CFINSERT and CFUPDATE don't call stored procs > and we do almost all our db work via stored procs. > > With CFQUERY you can do CFQUERYPARAM to help protect your db inputs > better, > set VARCHAR length, set NULLs, etc... > > But the dealbreaker for CFINSERT is that it won't return back the new > identity. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:11:2614 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/11 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:11 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.11 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
