From: <ch...@co...> - 2004-04-27 20:40:35
|
I don't have the code in front of me to refer to right now but I do believe that I am using timestamp albeit as a domain -- don't know if that makes a difference. This allowed be to verify my table layout with sqlserver since domains can be used like #defines. I'll take a closer look later this evening but I'm quite certain that I'm using timestamp. I can verify whether the timestamp from my datetime is getting into the data base correctly -- I believe it is but pulling it out is where I am seeing the discrepancy. I'll let you know later when I can look at stuff and provide you with further information. Thanks for your quick reply and excellent work on the provider and for open source. Chris > Hello: > > >I using version 1.5 of Firebird.NET provider and I noticed that DateTime > >does not convert 100% therefore failing if used in CompareTo. What I > >noticed is that the time portion of the datetime is missing as indicated > >by the ticks count. For example .... > > > >Write to Firebird > >EntryDate {4/27/2004} System.DateTime ==> ticks ==> > >632186542302487500 > > > >Read from Firebird > >EntryDate {4/27/2004} System.DateTime ==> ticks ==> > >632186542300000000 > > > > That works for me, are you sure the field in the database is > a timestamp field ?? ( i know it's stupid question but i need > to ask it :) ), date only fields doesn't have the time ;). > > The only part that isn't handled in 1.5 version for a timestamp > field are the milliseconds (that is being done yet in 1.6) > > > > -- > Best regards > > Carlos Guzmán Álvarez > Vigo-Spain |