You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added test for bug #3439, fixed typo in fix for same.
Comment 19774
Date: 2014-04-24 18:45:06 +0200
From: Alex Shestakov <<shura.shestakov>>
The original patch also fixed a bug with parsing timestamps having negative timezone offsets (in _extract_timezone() function).
The new fix doesn't do it.
Also in the original patch I replaced python parsing code using string.split() with datettime.strptime() assuming that it will work significantly faster.
The original patch also fixed a bug with parsing timestamps having negative
timezone offsets (in _extract_timezone() function).
Now also fixed.
The new fix doesn't do it.
Also in the original patch I replaced python parsing code using
string.split() with datettime.strptime() assuming that it will work
significantly faster.
Redid fix for bug #3439, much more like attached patch.
The patch wasn't entirely correct (times don't have fractions), and
not complete (also did date in the same way).
The advantage of this patch is that it actually simplifies the code,
something I didn't appreciate earlier.
The (slight) disadvantage is that it expects the format of the time
zone to be exactly [+-]HH:MM, unlike the original which was slightly
more liberal (in intent, anyway -- there was a bug in it) but I guess
that's OK.
The text was updated successfully, but these errors were encountered:
Date: 2014-02-18 17:37:28 +0100
From: Alex Shestakov <<shura.shestakov>>
To: clients devs <>
Version: 11.17.9 (Jan2014)
CC: shura.shestakov
Last updated: 2014-05-22 09:52:20 +0200
Comment 19586
Date: 2014-02-18 17:37:28 +0100
From: Alex Shestakov <<shura.shestakov>>
Created attachment 266
fix_milliseconds
Python driver drops milliseconds from temporal data when reading from the database.
The attached patch fixes the problem for me.
Comment 19771
Date: 2014-04-24 17:09:47 +0200
From: MonetDB Mercurial Repository <>
Changeset f2bbeac41f80 made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f2bbeac41f80
Changeset description:
Comment 19772
Date: 2014-04-24 17:17:26 +0200
From: MonetDB Mercurial Repository <>
Changeset a1c694f27eeb made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a1c694f27eeb
Changeset description:
Comment 19774
Date: 2014-04-24 18:45:06 +0200
From: Alex Shestakov <<shura.shestakov>>
The original patch also fixed a bug with parsing timestamps having negative timezone offsets (in _extract_timezone() function).
The new fix doesn't do it.
Also in the original patch I replaced python parsing code using string.split() with datettime.strptime() assuming that it will work significantly faster.
Comment 19775
Date: 2014-04-24 19:25:37 +0200
From: @sjoerdmullender
(In reply to comment 3)
Now also fixed.
I'll need to look into that claim.
Comment 19778
Date: 2014-04-24 22:10:34 +0200
From: MonetDB Mercurial Repository <>
Changeset 4bd5465d5ced made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4bd5465d5ced
Changeset description:
The text was updated successfully, but these errors were encountered: