This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-05
Channels
- # architecture (2)
- # aws (1)
- # bangalore-clj (4)
- # beginners (97)
- # boot (35)
- # cider (8)
- # cljsjs (3)
- # cljsrn (35)
- # clojure (190)
- # clojure-dusseldorf (4)
- # clojure-italy (7)
- # clojure-poland (1)
- # clojure-russia (17)
- # clojure-spec (74)
- # clojure-uk (30)
- # clojureremote (2)
- # clojurescript (298)
- # code-reviews (18)
- # component (18)
- # cursive (18)
- # datascript (3)
- # datavis (2)
- # datomic (24)
- # dirac (17)
- # emacs (3)
- # garden (7)
- # hoplon (51)
- # jobs (2)
- # jobs-rus (2)
- # leiningen (4)
- # luminus (11)
- # mount (24)
- # off-topic (1)
- # om (32)
- # onyx (25)
- # pedestal (1)
- # powderkeg (9)
- # protorepl (6)
- # re-frame (11)
- # reagent (15)
- # spacemacs (6)
- # sql (35)
- # uncomplicate (1)
- # unrepl (74)
- # untangled (130)
- # yada (6)
@scknkkrer are you getting error messages? Or mucking up strings? Or...what's going on that is making it just "not work"
:db “olexi?characterSetResult=utf8mb4&characterSet=utf8mb4&collation=utf8mb4_unicode_ci” :useUnicode true :characterEncoding “UTF-8"
http://info.michael-simons.eu/2013/01/21/java-mysql-and-multi-byte-utf-8-support/ seems helpful
Also, what DB are you using and what version of that DB? (e.g., MySQL 5.5 doesn’t support full Unicode, even if you provide all the correct connection parameters)
But folks have asked for more details about your environment — which is good, basic debugging practice — what DB, what server version, what JDBC driver version, what does your db-spec look like, etc?
I would also recommend creating a small self-contained correct example — per http://www.sscce.org — and put it on GitHub (or in a Gist) so folks can take a look at the whole (small!) code to help you debug things.
:db “dbname?characterSetResult=utf8mb4&characterSet=utf8mb4&collation=utf8mb4_unicode_ci?characterEncoding=UTF-8” :useUnicode true :characterEncoding “UTF-8" :characterSet “utf8mb4” :collation “utf8mb4_unicode_ci”
That’s not a valid db-spec for java.jdbc so I assume that’s what Korma expects and it’s doing something under the hood to create a db-spec for java.jdbc.
Like I say, create a SSCCE without Korma, so you can verify what parameters you need in your db-spec with java.jdbc, to make this work.
You may also want to check the docs for the mysql-connector-java library to see if there are fixes in more recent versions that will work with MySQL Server 5.7.16. We’re using 5.1.39 at work I think. We can’t use the 6.0.x driver since it doesn’t seem to work with MySQL 5.5 / 5.6 which we’re still on.