Re: [libdbi-devel] Expose tm struct for DATETIME

2014-01-06 Thread Mike Rylander
Ah! Well, I stuck my foot right in my mouth, didn't I? I did not read the patch closely enough, please ignore the noise. On Mon, Jan 6, 2014 at 10:08 AM, Jan Engelhardt wrote: > On Monday 2014-01-06 15:57, Mike Rylander wrote: > >>While I can certainly understand the desire to improve handling

Re: [libdbi-devel] Expose tm struct for DATETIME

2014-01-06 Thread Jan Engelhardt
On Monday 2014-01-06 15:57, Mike Rylander wrote: >While I can certainly understand the desire to improve handling of >dates and times in libdbi (I helped a bit with the timezone code a few >years back), I think breaking the API for all current applications is >a bit heavy handed. Thanks for your

Re: [libdbi-devel] Expose tm struct for DATETIME

2014-01-06 Thread Mike Rylander
While I can certainly understand the desire to improve handling of dates and times in libdbi (I helped a bit with the timezone code a few years back), I think breaking the API for all current applications is a bit heavy handed. How about a parallel API for grabbing the struct instead? That way yo

[libdbi-devel] Expose tm struct for DATETIME

2014-01-05 Thread Jan Engelhardt
I have a 2-patch here which I would like to share before merging. SQL databases such as Mysql support dates from 1000-01-01 to -01-01. However, even "reasonable" dates like 1968-02-14 cannot be reliably retrieved through libdbi. The root problem is that time_t only starts at 1970, and MSVCRT