This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-21
Channels
- # announcements (6)
- # bangalore-clj (1)
- # beginners (46)
- # cider (21)
- # cljs-dev (30)
- # cljsjs (3)
- # clojure (131)
- # clojure-dev (20)
- # clojure-europe (2)
- # clojure-italy (12)
- # clojure-nl (11)
- # clojure-russia (4)
- # clojure-spec (55)
- # clojure-uk (57)
- # clojurebridge (1)
- # clojured (1)
- # clojurescript (55)
- # cursive (11)
- # data-science (1)
- # datomic (23)
- # duct (1)
- # emacs (1)
- # events (1)
- # figwheel-main (2)
- # fulcro (219)
- # graphql (16)
- # immutant (1)
- # jackdaw (3)
- # java (6)
- # juxt (30)
- # kaocha (8)
- # mount (3)
- # nyc (1)
- # off-topic (16)
- # pathom (48)
- # pedestal (1)
- # re-frame (71)
- # reagent (17)
- # ring-swagger (3)
- # shadow-cljs (96)
- # spacemacs (21)
- # specter (8)
- # speculative (20)
- # sql (21)
- # test-check (2)
- # tools-deps (12)
- # vim (6)
Hola! When would 0.7.9 version seem likely for release? We are using 0.7.6 because of this issue: https://dev.clojure.org/jira/browse/JDBC-176, would like to jump onto a newer version to avoid confusion within the team ๐
@viesti I wasn't planning to release 0.7.9 once I've figured out what to do about https://dev.clojure.org/jira/browse/JDBC-174
At this point, I'm leaning toward just updating the docstring to caution about DB-specific behavior/options and punting on a better solution in next.jdbc
.
I'll set myself a reminder to deal with this tomorrow at work since we moved my main scheduled task from tomorrow to next Tuesday ๐
nothing is burning at our side, just wanted to quickly ask about the 0.7.9, so no worries, thanks for the reply ๐
I'll need to update docs etc for these three anyway https://dev.clojure.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JDBC+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide and then cut a release.
org.clojure/java.jdbc 0.7.9
is headed to Maven Central. Will announce in several places once it shows up there later today.
Here's what's in it: Changes in 0.7.9 Fix behavior of multi-inserts when database does not support generated keys JDBC-176. Added highly experimental support for datafy/nav (in clojure.java.jdbc.datafy namespace). This includes a convention-based approach to foreign keys with some assistance from a :schema option. This is subject to change and is provided mostly for informational purposes, as an example of the new functionality in Clojure 1.10. This includes a fix for the conventions from JDBC-175. Add note about rewriting batched operations to insert-multi! for some drivers JDBC-174. Support Oracle SID style URLs (dbtype can be oracle:sid which maps to oracle:thin and uses : as the separator before the dbname value) JDBC-173.
Thanks for the nudge. We've not been in need of the 0.7.9 changes at work and I've been so focused on next.jdbc
that I had forgotten about it.
I have this piece of sql that works with Mariadb but cause Mysql 5.7 to yell invalid syntax https://gist.github.com/myguidingstar/d3e861f1ea895a27d826f898e4cbe728
what's the problem?
it's funny that cow/index
becomes cowindex
in the error message
CTEs are new in MySQL 8, aren't they? So 5.7 doesn't support them.
Yup, confirmed. New in 8, not available in 5.7.