> I wouldn't know either way, as I don't use SQL server. As I said, I've
heard the argument. Nothing more.
scandalous behavior in repeating it ;-)
> You know dbs inside and out, Paul. What is your opinion of the best way
to accomplish the task, if you're stuck with something like Access or mySQL?
What do you think of the CF_max_ID tag the original poster was mentioning?
i wouldn't say that i know dbs "inside & out", i know something about
sql server because thats what i chose to use (best bang for the buck
with the fewest management headaches in my market). i chose not to
use access for reasons you've heard me spout on enough about in the
cf forums. i chose not to use mysql more for their attitudes about the
missing "luxury" items (triggers, sp, transaction granularity, etc., we
didn't build them into mysql, therefore you don't need them, blah blah
blah) than for the fact these things were missing--though not having these
tools is still fatal to me. i guess they're singing another song now.
if you can live w/2 queries:
insert into autonumber table.
re-query for that row, returning autonumber.
if nothing in that row but the autonumber makes it
unique, than *add* (not replace) in a column to hold
a UUID (which you'd build in cf prior to inserting) and
query for that. keep the int autonumber for JOINs.
if you can live with more than 2 queries (though the 1st 2 should
be short & sharp):
use a key table to manage these IDs.
i suppose if you were clever enough you could load this into
an application/server scope structure & periodically refresh
the physical table....provided no non-cf processes hit that
table.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
