If you decide to go in this direction, I would suggest not just using the 'datetime' added column. create a truly unique identifier such as: "datetime (YYYYMMDDHHMMSS)+ user ip address (or username if logged in) plus a random sequence". This way you will know you can search on the unique and not get a possible duplicate.
However, you can also create a separate set of functions (CFCs) for each possible database so that you only hit the database once per call, if you want to blend the need for optimized code along with database type independence. William >What I'm thinking, from this thread and others I've read in the past, >is that if keeping your code database-independent is priority..... >inserting some unique identifier and then querying for that in a second query >...might be the best option. > >Or do you folks find that you can't really stay uncoupled from your DB? > > > > >> issue, but it is definitely something that must be kept in mind. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:311512 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
