Fluent NHibernate SqlDateTime overflow exception

Question

I'm mapping a very simple Users table, and i have a column named 'LastLoginDate' which is defined as nullable in sql server.

My mapping looks like this :

public Users {
    Id(x => x.UserId);
    Map(x => x.UserName);
    ...
    ...
    Map(x => x.LastLoginDate).Nullable();
}

But everytime I try to save this entity programatically, i always get the SqlDateTime overflow exception. If i try to enter a manual sql statement with 'null' in this column it works. If i comment out just this property, it will work as well.

What can be the problem ???

Thanks in advance!

Jim Schubert · Accepted Answer · 2010-04-24 18:34:23Z

12

Your entity should look like this:

public class User
{
   public virtual DateTime? LastLoginDate {get;set;}
   // etc
}

Then, your map should work properly.

edit: The ? after DateTime specifies that it is Nullable, and is a short form for Nullable<DateTime>. If this isn't the cause of your error, you may want to check that Fluently.Configure specifies the correct version of SqlServer.

answered Apr 24, 2010 at 18:34

Jim Schubert

20.4k5 gold badges64 silver badges69 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

gillyb Over a year ago

WOW, i feel so stupid now!... Sometimes it's so hard to see that you forgot something so trivial and small :) Thanks!

Jim Schubert Over a year ago

No problem, I do it all the time. Sometimes you just need a second pair of eyes.

Jonathan Over a year ago

I'm having exactly the same problem, but making DateTime nullable simply isn't working for me. Not sure what could be wrong.

Jim Schubert Over a year ago

I'd double check that the column is marked nullable in the database. If it is, clean your solution and rebuild. Also, if you're using SQL Server 2008 it may be a DateTime.MinValue see: stackoverflow.com/questions/5425610/… In that case, you'll need to override: stackoverflow.com/questions/5506524/…

Frank Bell Over a year ago

If still having problem after clean and rebuild, another thing to do is clear the second level cache. In my case the DateTime.MinValue was held in the cache and kept on getting re-applied as the data was read from the cache.

Collectives™ on Stack Overflow

Fluent NHibernate SqlDateTime overflow exception

1 Answer 1

5 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

5 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related