A trigger is going to run on an INSERT/UPDATE/DELETE
of a table.
So you would have to go through the trouble of
getting a stored procedure to write to a file.
It is probably easiest to just Update or Insert
into your table and any time you need to make a
log of the table write the file based on the new
query.
Caching the query wont work since the data will be
constaly changing, you would constalty recache the
query and then write to the file which would be..
less effecient unless you are doing mulitple
file writes or reusing that query many times.
But if you need realtime data changes a cached
query will not work so well. So really if you go
through the trouble of getting the trigger to work
it may or may not be more effecient, it is
going to be far easier to just let CF write the
file when you update/insert/delete from the
table.
Jeremy Allen
[EMAIL PROTECTED]
[Insert cool title here]
-----Original Message-----
From: Michael Slatoff [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 16, 2000 12:30 PM
To: [EMAIL PROTECTED]
Subject: SQL Trigger vs. Stored Procdure
I am considering using a trigger to write .csv file when a column
changes. I will then include that file and use it to loop over.
The question is...
Is this more efficient or less efficient than using a cached query?
Michael Slatoff
www.slatoff.com
----------------------------------------------------------------------------
--
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
