....lets nip this myth in the bud....
> But what is the query that queryName refers to?
the cfquery for the original insert.
> Are you saying that CF is clever enough to pick up the fact that the
> trigger has fired & grab the value from somewhere?
no, but ODBC & sql server are...
> The SQL Server documentation says:
since we're quoting (BoL):
"When a trigger fires, results are returned to the calling application, just
as with stored procedures."
> <QUOTE>
> Triggers can include any number and kind of Transact-SQL statements except
> SELECT. A trigger is designed to check or change data based on a data
> modification statement; it should not return data to the user.
> </QUOTE>
where does this bit come from? BoL only *suggests* you refrain from
returning results w/triggers because it would require all applications
accessing that table be able to handle the returned results.
> <QUOTE>
> To eliminate having results returned to an application due to a trigger
> firing, do not include either SELECT statements that return results, or
> statements that perform variable assignment in a trigger. A trigger that
you've taken this out of context. see the 1st line for this "quote" above.
triggers do have their place in development toolboxes.
------------------------------------------------------------------------------
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.
