DUAL?!?!!? That works, and is magic, but, again: ?!?!? I'll have to
research this. I am sure there is a good reason for it being called
DUAL. If not, and if this is truly arbitrary, then I am disappointed
that the folks at Oracle didn't come up with some more colorful name,
like SPAGHETTIFLASHLIGHT or ARNOLD.
Thanks! This works wonderfully.
Matthieu
Ian Skinner wrote:
When I have run into this, having to put a incremental key value into
several tables, what I have done is select the WIDGETS_PKSEQ.NEXTVAL and
then use that value in all my inserts. Somewhat like this off the top
of my head example.
<cfquery name="nextKeyVal" ...>
SELECT
WIDGETS_PKSEQ.NEXTVAL AS KEY
FROM dual /*I believe this is the proper 'table'*/
</cfquery>
Then I can refer to nextKeyVal.Key in all my inserts. I wrap this all
up in a <cftransaction> block so that if a problem occurs I hopefully
don't end up with 1/2 the data saved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:223059
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=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
