In my experience, even the most unlikely thing will happen.
I like to re-select using the same criteria as the insert.
Wheter you do it the above way, or the select max ID way,
I'd surround the code with a CFTRANSACTION tag. That be extra
careful to prevent collisions.
David Cummins wrote:
>
> The most reliable way as far as I can see is to select the max id using the
> exact criteria. I mean, come on, how likely is a collision?
>
> David Cummins
>
> Rob Keniger wrote:
> >
> > on 6/12/00 10:24 PM, DeVoil, Nick at [EMAIL PROTECTED] wrote:
> >
> > > There is no way of doing this with MySQL AFAIK,
> > > not via ODBC anyway.
> > >
> > > Maybe instead of an autonumber you could generate
> > > a quasi-unique ID using some other info - timestamp,
> > > user name, whatever.
> >
> > I have used this method before, using CreateUUID(). Pretty hefty for an ID
> > but it works.
> >
> > I have also done a SELECT back on the table using the exact criteria I have
> > just INSERTed. Obviously this will not work in all cases.
> >
> > Unfortunately the only alternative is to lock tables which is bad bad bad.
> >
> > --
> >
> > Rob Keniger
> >
> > big bang solutions
> >
> > <mailto:[EMAIL PROTECTED]>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
