That is very nice Brad. Thanks for that perspective.
>First of all, it is my preference to explicitly check for an existing
>duplicate value prior to insertion instead of allowing SQL server to
>throw the error. The column constraint is my fall-back.
>Either way, if you want your stored pr
On Wed, Aug 26, 2009 at 4:04 PM, Tony Bentley wrote:
>
>
> When this is thrown, the message states "[Macromedia][SQLServer JDBC Driver]"
> and then the RAISERROR message following. Nice for debugging but not so nice
> for passing the message and error code to a handler.
>
> I would really like t
> A real world scenario is when a user tries to insert a value that must be
> unique in the database. If a duplicate
> is found, SQL can return a reference code and a message stating that there is
> a duplicate found, an exception
> is thrown and an id is passed back - RAISERROR & @@ERROR.
>
> W
ms may have occurred. You can then use the value of
@outputMessage to return to the user if you so choose.
~Brad
Original Message ----
Subject: Re: CFSTOREDPROC kind of sucks
From: Tony Bentley
Date: Wed, August 26, 2009 3:04 pm
To: cf-talk
Sorry, only two issues really.
Sorry, only two issues really.
A real world scenario is when a user tries to insert a value that must be
unique in the database. If a duplicate is found, SQL can return a reference
code and a message stating that there is a duplicate found, an exception is
thrown and an id is passed back - RAI
On Wed, Aug 26, 2009 at 2:14 PM, Tony Bentley wrote:
>
> dbvarname is completely useless. It would be nice to be able to send values
> across out of order or not send a value if it is not needed (NULL). It would
> also be nice to have those values in the debugging to reference.
You can send a n
According to LiveDocs, in MX 6 "Changed the dbvarname attribute
behavior: it is now ignored for all drivers. ColdFusion uses JDBC 2.2
and does not support named parameters."
Thanks,
Eric Cobb
http://www.cfgears.com
Dave Watts wrote:
>> Three issues that come to mind:
>
> You've really only
> Three issues that come to mind:
You've really only listed two issues.
> Cannot access transaction errors because a coldfusion exception is thrown so
> any validation exceptions must be
> handled through cftry/cfcatch instead of the CFSTOREDPROC. If en error occurs
> in SQL, it means coldfusi
Three issues that come to mind:
Cannot access transaction errors because a coldfusion exception is thrown so
any validation exceptions must be handled through cftry/cfcatch instead of the
CFSTOREDPROC. If en error occurs in SQL, it means coldfusion throws an error
too.
dbvarname is completely
9 matches
Mail list logo
