Re^2: difference between syb_nsql and prepare/execute call

Replies are listed 'Best First'.
Re^3: difference between syb_nsql and prepare/execute call by Anonymous Monk on Nov 09, 2010 at 17:52 UTC
I don't know about you, but I read that as saying there are trade-offs.	[reply]
Re^4: difference between syb_nsql and prepare/execute call by perl@1983 (Sexton) on Nov 09, 2010 at 18:55 UTC
So, which one would you prefer? syb_nsql or prepare/execute?	[reply]
Re^5: difference between syb_nsql and prepare/execute call by Anonymous Monk on Nov 09, 2010 at 21:05 UTC
Generally, the programs I'm asked to write use a handful of known SQL statements called several times with varying bound parameters. In those situations, prepare/execute has definite speed advantages. If you're only going to use a statement once during the life of the program (or connection), those advantages fade away. In that case there can be advantage, or at least convenience, in an all-in-one statement. So without knowing your particular use case, I'm sorry to say I can't make your decision for you.	[reply]
Re^5: difference between syb_nsql and prepare/execute call by elwarren (Priest) on Nov 10, 2010 at 14:13 UTC
I use DBD::Oracle for most of my work, so I prefer prepare/execute ;-)	[reply]