SCM

[#1010733] TimeStampTZ: NpgSql doesn't seem to account for timezones with 1/2 hour offsets

View Trackers | Bugs | Download .csv | Monitor

Date:
2009-11-24 00:30
Priority:
3
State:
Open
Submitted by:
Daniel Le (blacktx)
Assigned to:
Nobody (None)
Npgsql Version:
2.0
Category:
Group:
Resolution:
None
Summary:
TimeStampTZ: NpgSql doesn't seem to account for timezones with 1/2 hour offsets

Detailed description
Here's the stack trace that would help you find the problem as per previous threads:

at System.DateTimeParse.ParseExactMultiple(String s, String[] formats, DateTimeFormatInfo dtfi, DateTimeStyles style)
at System.DateTime.ParseExact(String s, String[] formats, IFormatProvider provider, DateTimeStyles style)
at NpgsqlTypes.BasicBackendToNativeTypeConverter.ToDateTime(NpgsqlBackendTypeInfo TypeInfo, String BackendData, Int16 TypeSize, Int32 TypeModifier)
at NpgsqlTypes.NpgsqlBackendTypeInfo.ConvertToNative(String BackendData, Int16 TypeSize, Int32 TypeModifier)
at NpgsqlTypes.NpgsqlTypesHelper.ConvertBackendStringToSystemType(NpgsqlBackendTypeInfo TypeInfo, String data, Int16 typeSize, Int32 typeModifier)
at Npgsql.StringRowReaderV3.ReadNext()

At this point, with the Newfoundland Standard time, and at ISO, MDY dateStyle, I get the following when I perform a "select now();" command:

"2009-11-11 20:15:43.019-03:30"

If there are any clarifications whatsoever, please let me know! I'll be glad to provide you with any information that I have.

Daniel

Followup

Message
Date: 2009-12-18 02:00
Sender: Daniel Le

Thanks a lot!
Date: 2009-12-18 01:51
Sender: Francisco Figueiredo jr.


The module name is Npgsql2

I hope it helps.
Date: 2009-12-18 00:46
Sender: Daniel Le

Alright, I was able to get cvs up and running...

I think that I need the module name now.

If you could help me out with that, it would be grand...

Many thanks!!
Date: 2009-12-15 01:36
Sender: Josh Cooley

You can follow the minimal instructions here for downloading from cvs (requires a cvs client).
http://pgfoundry.org/scm/?group_id=1000140

But to simplify things, I've attached a build from my copy of source. It includes the fix from CVS as well as some other bits that are works in progress. This build shouldn't be considered useful for anything other than for testing this fix. It's a build targeting .NET 3.5 sp1.
Date: 2009-12-15 01:19
Sender: Daniel Le

I'm sorry, I'm a mediocre programmer, and even worse when
working with CVS.

When you say that the fix is in CVS, does this mean that the
dll is available for me to fetch?

If so, would you be able to give me the path of the dll?

Thanks
Date: 2009-12-13 03:31
Sender: Josh Cooley

I had originally expected to fix parsing for the DateTime, but as part of another bug fix I completely changed the Npgsql type support system. You'll find this fix in CVS now. Parsing now goes through NpgsqlTimeStampTZ. The parses the values correctly and then converts it to a DateTime value if you aren't using the provider specific types.
Date: 2009-11-25 23:16
Sender: Daniel Le

I'm currently using 2.0.6
Date: 2009-11-25 20:20
Sender: Gildas

hi,

just one more thing, what is your npgsql version ?


Attached Files:

Changes:

No Changes Have Been Made to This Item

Powered By FusionForge