Re: SqlParameter and DBNull.Value - possible bug?
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Wed, 14 May 2008 11:41:14 -0400
Martin Ret wrote:
Is following behaviour by design or is it a bug?
For shure breaking change from framework 1.1.
Try under framework => 2.0
SqlParameter param = new SqlParameter("Test", DbType.Int32);
Console.WriteLine("Value: {0}, Type: {1}",param.Value, param.DbType);
param.Value = DBNull.Value;
Console.WriteLine("Value: {0}, Type: {1} --- WTF",param.Value,
param.DbType); Console.ReadLine();
There was no way for you to know it (except maybe by browsing through
some of the previous questions in this newsgroup before posting yours -
always a recommended practice) , but this is a classic (COM-based) ADO
newsgroup. ADO.Net bears very little resemblance to classic ADO so,
while you may be lucky enough to find a dotnet-knowledgeable person
here who can answer your question, you can eliminate the luck factor by
posting your question to a group where those dotnet-knowledgeable people
hang out. I suggest microsoft.public.dotnet.framework.adonet.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
.
- References:
- SqlParameter and DBNull.Value - possible bug?
- From: Martin Ret
- SqlParameter and DBNull.Value - possible bug?
- Prev by Date: SqlParameter and DBNull.Value - possible bug?
- Next by Date: Re: Non initialized Cmd Parameter Collection via ASP vs SQL Server
- Previous by thread: SqlParameter and DBNull.Value - possible bug?
- Index(es):
Relevant Pages
|
Loading