Howie, In most situations, you're probably not going to have a key defined or will have a default key indicating that the record hasn't been committed. Why not just cfif on that?
-joe On Wed, 2 Feb 2005 16:50:41 -0500, Howie Hamlin <[EMAIL PROTECTED]> wrote: > I have an application where I want to update an exising record or create it > if it doesn't exist (this is for keeping daily stats). The table is indexed > and does not allow dupes. I came up with something like this: > > <cftransaction> > <cftry> > insert record > <cfcatch type="any"> > update record > </cfcatch> > </cftry> > </cftransaction> > > Basically, if the insert fails then I assume that there is a key violation > and I update the existing record. Does anyone see a problem with this? My > thought was that if you do a select first to see if the record exists and > then either insert a new record or update the exising record then that would > still take two trips to the SQL server. > > Thanks, > > Howie > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:192825 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
