Dario,
I've updated NH-1973 with the latest version of the test case.
I'll have a look in the NH code to see if I can work out how to fix
it, but I've only just downloaded the codebase and haven't even got it
to compile yet ;)
--~--~-~--~~~---~--~~
You received
Graham,If you copypaste the explication you have sent to the dev-list in
the NH-1973 ticket would be fine.
Don't worry about the fix (it is easy for us).
2009/9/27 Graham Bunce grahambu...@hotmail.com
Dario,
I've updated NH-1973 with the latest version of the test case.
I'll have a look in
Thanks !
I will have a look soon.
Cheers ;)
On Sun, Sep 27, 2009 at 7:24 AM, Graham Bunce grahambu...@hotmail.comwrote:
Dario,
I've updated NH-1973 with the latest version of the test case.
I'll have a look in the NH code to see if I can work out how to fix
it, but I've only just
Submit a patch with the failing test to our jira: jira.nhforge.org
Thanks!
On Sat, Sep 26, 2009 at 7:54 AM, Graham Bunce grahambu...@hotmail.comwrote:
Oskar. Yes I have, and my test fails to confirm it.
using (ISession session = this.OpenSession())
{
This is just a guess, but is it possible that SQL profiler may not
print the full value? Have you checked the actual stored value?
/Oskar
2009/9/26 Graham Bunce grahambu...@hotmail.com:
All,
I raised a bug (NH-1973) which someone kindly pointed out was a
limitation in SQL Server. My
Oskar. Yes I have, and my test fails to confirm it.
using (ISession session = this.OpenSession())
{
DomainClass entity = session.GetDomainClass(1);
Assert.AreEqual(DateTime.Parse(2009-09-23 16:28:21.489),
entity.Timestamp);
}
