WilsonORMapper : Forums

Home

WilsonORMapper > Forums

	Demo Version
Download and try for yourself a fully working demo version, including sample apps and documentation. The only limitation is that the demo version only works inside the debugger.

	Subscribe
Get It All for $50 USD: WebPortal, ORMapper, Source Code, All Updates

User Login

Log In
User Name:
Password:
Remember me next time.

Reset Password

Wilson ORMapper Forums : Bugs & Issues : nullValue with dates

Reply To Thread

Date

Post

11/29/2006 6:42:25 PM

when i update a date previously null, it keeps on changing it to 01/01/1975

I attempted to add the following attribute without success:

nullValue="1/1/1753"

I am using 4.2.2.0 version (latest)

11/30/2006 9:36:11 PM

What database are you using? Any special locale or regional settings I should know about? Using nullValue="1/1/1753" should work, or just nullValue="DateTime.MinValue". If you are using .NET v2.0 then I prefer nullable types, in which case you don't specify a nullValue but you declare your member as a nullable (DateTime? in C#).

Thanks, Paul Wilson