This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have just turned on entity time tracking and it is breaking on entities that use class table inheritance. Note that I have turned it on both for the base entity and the derived entity.
[Test]
System.Data.SqlTypes.SqlTypeException : SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM.
|
|
|
I did some more testing and have some more info for you: It works when I save a new base entity to the database but not the derived entity. |
|
|
Thanks for reporting this. It is not necessary to turn on time tracking at each level of the hierarchy. Just turn it on in the base class and leave it off in the derived classes. The derived classes inherit the CreatedOn and UpdatedOn properties so you can still access and query on the time fields through the derived classes. |
|
|
Ok. Could you add a more user friendly error message in case another developer working with the model does the same thing. |
|