ODP.NET Stored Procs and Optional Parameters?

AFAIK the BindByName is intended for use in cotrast to binding by position... it has nothing to do with any default params or similar.

AFAIK the BindByName is intended for use in cotrast to binding by position... it has nothing to do with any default params or similar...

Thanks. So if there are optional parameters in your SP you have to send them in through ODP. NET regardless, right?

– VBCSharp Sep 8 at 18:26 yes - that's what I gather... – Yahia Sep 8 at 20:22.

In my experience, BindByName does not work for stored procedures - only for queries. But it really shouldn't matter to you. You should only be calling this SP from a single method in your application anyway.

Use default parameters in the signature of that method, and just always pass all parameters to ODP.Net. Object GetFoo(DateTime pubDate, string fName = null, string lName = null, string phone = null) { } Do that, forget about it and use your time for more important problems.

By default, the binding to Oracle Parameters in a stored procedure is based only on position. This means that you have to add your parameters in the same order as they are declared in the procedure and Oracle will not care about the name you set your parameter to. When you set the binding to BindByName, you can add parameters in any order, as long as they have the same name.

This is, in my opinion a lot better than the default. However, setting BindByName to True or False won't affect wether a parameter is required or no.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.