Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time format differences between 32-bit and 64-bit builds #7

Open
ghost opened this issue Aug 31, 2012 · 0 comments
Open

Time format differences between 32-bit and 64-bit builds #7

ghost opened this issue Aug 31, 2012 · 0 comments

Comments

@ghost
Copy link

ghost commented Aug 31, 2012

It appears that the 32-bit time has less resolution than the 64-bit build. The time format used in the 64-bit build is "2006-01-02 15:04:05.000000-07" while the format returned in 32-bit builds is "2006-01-02 15:04:05.00000-07" (five zeros in the decimal portion instead of six).

I am having difficulty narrowing it down to PostgreSQL or the library. Either way, my development machines is CentOS 6.3 64-bit and my production machine is Centos 6.4 32-bit. Both systems are using PostgreSQL 8.4.12. The built binary runs fine on my development machine, but fails on the production machine. Here is the error:

parsing time "2012-08-31 21:08:57.37711+00" as "2006-01-02 15:04:05.000000-07": cannot parse "00" as ".000000"

I scan the values into object variables and then parse the text (time.Parse()) to get a time.Time object. I really need to use the time.Time stuff for math reasons.

Please let me know if there's any further information I can provide to resolve this. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants