Re: SqlParameters anomoly
stewartmclean_at_supanet.com
Date: 12/10/04
- Next message: Andrew Fisher: "Re: Why does this work???"
- Previous message: Ray Manning: "Re: Accessing value type static members via instance?"
- In reply to: jdmartinez_at_ea.com: "Re: SqlParameters anomoly"
- Next in thread: jdmartinez_at_ea.com: "Re: SqlParameters anomoly"
- Reply: jdmartinez_at_ea.com: "Re: SqlParameters anomoly"
- Messages sorted by: [ date ] [ thread ]
Date: 10 Dec 2004 01:39:31 -0800
Hi Joel,
>>From what Ive tried, its only ' 0 ' that gets interpretted as null. The
code:
cmd.Parameters.Add("@myintparam", 0);
acts exactly as
cmd.Parameters.Add("@myintparam", null);
any other int gets treat as an int, as you'd expect. The second
parameter of .Add takes an object, so its either something I dont
understand about boxing, or a bug. I cant imagine its by design.
- Next message: Andrew Fisher: "Re: Why does this work???"
- Previous message: Ray Manning: "Re: Accessing value type static members via instance?"
- In reply to: jdmartinez_at_ea.com: "Re: SqlParameters anomoly"
- Next in thread: jdmartinez_at_ea.com: "Re: SqlParameters anomoly"
- Reply: jdmartinez_at_ea.com: "Re: SqlParameters anomoly"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|