> Given that the patch just > provides a way for users to tell the library "these columns are > special", it seems like you might just as well map a column adjustment > function over the result set yourself? It feels very clunky.
The JDBC library requires us to treat these columns special. If we don't call the right getter function, then it will return the wrong Date instance. It is very clunky to use Date instances created in the wrong timezone. > It also looks like it can reorder columns. These special columns will only get inserted into the regular map at the end, but after all, it's a regular map and this will only happen if we make these columns special by passing in the optional parameter. The patch is fully backward compatible. > Overall, I still think this problem arises because you're not > following best practices for managing timezones which is to have all > your servers operating on the same timezone and using NTP to sync > times What if I am using the JDBC library in a client software instead of being in the server? On Tuesday, 31 July 2012 12:22:23 UTC+8, Sean Corfield wrote: > > On Fri, Jul 27, 2012 at 10:42 AM, Jestine Paul > <jestin...@gmail.com<javascript:>> > wrote: > > I have raised a JIRA issue (JDBC-35) regarding the timezones returned > from > > the ResultSet getter method. > > http://dev.clojure.org/jira/browse/JDBC-35 > > I'm a bit surprised no one has responded to this. Maybe no one else is > having this issue? I'd love to see some feedback on this. > > > I have also attached a patch to this issue. > > > http://dev.clojure.org/jira/secure/attachment/11394/resultset-timezone.diff > > I hope there are better solutions suggested. Given that the patch just > provides a way for users to tell the library "these columns are > special", it seems like you might just as well map a column adjustment > function over the result set yourself? It feels very clunky. > > It also looks like it can reorder columns. java.jdbc used to use > structmap to preserve column order but now uses regular maps - > although small maps use an array map which does in fact preserve > column ordering for reasonable numbers of columns. That didn't seem to > be particularly important for users at the time but gratuitous > partitioning of columns seems unnecessary... > > Overall, I still think this problem arises because you're not > following best practices for managing timezones which is to have all > your servers operating on the same timezone and using NTP to sync > times - but I really do want to hear some feedback from other > java.jdbc users (which is why I haven't just closed the ticket). > -- > Sean A Corfield -- (904) 302-SEAN > An Architect's View -- http://corfield.org/ > World Singles, LLC. -- http://worldsingles.com/ > > "Perfection is the enemy of the good." > -- Gustave Flaubert, French realist novelist (1821-1880) > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
