OracleCommadbuilder: Exception: Parameter 'p1': No size set for variable length data type: String.

  • Thread starter Thread starter Peter Meinl
  • Start date Start date
P

Peter Meinl

When updating an Oracle Varchar2 column with an empty string "" using the
OracleCommandBuilder generated UpdateCommand the follwing error is thrown:
"Parameter 'p1': No size set for variable length data type: String."

Is this a bug in the OracleCommandBuilder? Is there an elegant workaround?

Updating with DBNull.Value instead of an empty string does not throw the
above error.
 
Hello,

I am re-raising this post as we have a developer here running into the same issue. Is this a bug or a feature? Are there any similar bugs or features of other datatypes that we should be aware of?

Thanks!
 
Hello,
yes, this is a bug in the current version of Visual Studio .net and should
be fixed in the next one.

Best regards

Ryszard Gawron
Microsoft Developer Support

This posting is provided "AS IS" with no warranties, and confers no
rights.

ASP.NET said:
Hello,

I am re-raising this post as we have a developer here running into the
Click to expand...
same issue. Is this a bug or a feature? Are there any similar bugs or
features of other datatypes that we should be aware of?
 
As a workaround it is OK to send DBNull.Value instead of an empty string.
Oracle transforms emtpy strings to Null anyway.
 
I have .NET Framework 1.1 SP1 (just recently released) installed and still get this message. Worse, when I try to use ODP (directly from Oracle), I am getting a "Concurrency violation: the UpdateCommand affected 0 records." In this situation. Can anyone shed light on this strange error?
 
Can you send a code-snippet that will help us solve the problem?
--
HTH,
Sushil Chordia.
This posting is provided "AS IS" with no warranties, and confers no rights.
SqlJunkies User said:
I have .NET Framework 1.1 SP1 (just recently released) installed and still
Click to expand...
get this message. Worse, when I try to use ODP (directly from Oracle), I am
getting a "Concurrency violation: the UpdateCommand affected 0 records." In
this situation. Can anyone shed light on this strange error?supports Post Alerts, Ratings, and Searching.
 
Back
Top