I am assuming you are using this value to imply that the field has "no" value, and for most databases, that is the NULL value. I recommend modifying the domain object to make the field a nullable DateTime (DateTime?). -Brian
2009/9/23 江名峰 <[email protected]> > why you need a DateTime value like'1/1/0001' ? we can set the value as > default value(getdate()) on SQL,then don't allow insert on NH mapping. > > 2009/9/23 Jason Dentler <[email protected]> > >> It depends how the date value is stored internally by the database engine. >> This varies widely between database engines and sometimes between versions. >> >> >> On Tue, Sep 22, 2009 at 1:11 AM, Kris-I <[email protected]> wrote: >> >>> >>> I use SQL Server 2008 ..... but with this >>> NHibernate.Dialect.MsSql2005Dialect it's probably the problem. >>> >>> Is there this kind of limitation with other database ? >>> >>> >>> > this is a limitation of SQL Server < 2008. >>> > in 2008 there's a new data type, datetime2, that AFAIK can handle a >>> .NET >>> > DateTime precisely. >>> >>> >>> >> >> >> > > > -- > 江名峰(James.Jiang) > msn：[email protected] > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
