Along with the other reasons listed, we found it politically expedient.
Several of our apps use legacy data from other divisions. By using stored
procedures, we were able to say:
"It's your data, you write the updates, we'll just hand you the
information."
They felt more comfortable with the control, and we didn't have to get our
hands dirty with details.
> John Hoskins
> TDS Computing Services
> Internet Technology Team
> [EMAIL PROTECTED]
> 608.664.8263
> 608.664.8288 (fax)
>
> ----------
> From: [EMAIL PROTECTED][SMTP:[EMAIL PROTECTED]]
> Sent: 6/4/1999 12.40 AM
> To: [EMAIL PROTECTED]
> Subject: [ND] Using Stored procedures for transaction management
>
>
>
>
> I'm not used to using stored procedures but recently I was looking over
> some
> one's ND4 code (for an app that talks to Informix 7) and I noticed that
> stored
> procedures were used whenever a series of INSERT/DELETEs needed to be
> executed
> as a transaction. That looked like a smart coding technique to me, and I'd
> like
> to get other opinions.
>
> Do you recommend using SPs like that? Pros/cons?
>
> Thanks!
> Janet
>
>
> _________________________________________________________________________
>
> For help in using, subscribing, and unsubscribing to the discussion
> forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
>
> For dire need help, email: [EMAIL PROTECTED]
>
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
