If you are talking about DateTimeType.cs it is a bug even if the best
candidate to represent a DateTime is TimeStamp.Please:
Create a JIRA with Affects version 2.0.1GA
Create a little test
Fix the bug in 2.0.x branch
Fix the bug in trunk
Close the JIRA with "Fix/Version" 2.0.2.GA (the actual 2.0.x branch)
NOTE:
Probably we don't have some specific test but for who are using a class with
a DateTime to represent a Date and without specify the type in the mapping
the fix of this issue will result in a Breaking Change. If you fix it please
remember to add something in the releasenotes.txt
Thanks.
2008/10/3 Will Shaver <[EMAIL PROTECTED]>
> Trying to get to the bottom of a huge bug (more on that later perhaps...
> when I figure out if it is NH or my code) I noticed that DateTimeType is
> only returning the Date part of the data and not the Time part for ToString
> and other operations. Any reason for this? I'd like to see it return
> everything as that's more useful in log files etc.
> Specifically:
>
> public override string ToString(object val)
> {
> return ((DateTime) val).ToShortDateString();
> }
>
> public
> override string ObjectToSQLString(object value, Dialect.Dialect dialect)
> {
> return "'" + ((DateTime)value).ToShortDateString() + "'";
> }
>
> It looks like these were copied long ago from the DateType and never
> updated. Java Hibernate does NOT have a DateTimeType. I'll change these to
> the full DateTimes unless someone has a reason they should not be...
>
>
>
> -Will
>
--
Fabio Maulo
