This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-28
Channels
- # ai (1)
- # beginners (239)
- # bitcoin (1)
- # boot (4)
- # cider (5)
- # clara (3)
- # cljs-dev (16)
- # cljsjs (5)
- # cljsrn (1)
- # clojure (152)
- # clojure-android (3)
- # clojure-dev (3)
- # clojure-greece (4)
- # clojure-italy (5)
- # clojure-spec (14)
- # clojure-uk (24)
- # clojurescript (81)
- # data-science (1)
- # datomic (47)
- # devcards (34)
- # docs (3)
- # emacs (6)
- # ethereum (1)
- # events (9)
- # flambo (5)
- # fulcro (11)
- # graphql (1)
- # immutant (3)
- # lein-figwheel (2)
- # leiningen (2)
- # luminus (6)
- # lumo (90)
- # off-topic (25)
- # proton (2)
- # re-frame (44)
- # reagent (5)
- # ring (7)
- # ring-swagger (11)
- # shadow-cljs (11)
- # spacemacs (6)
- # vim (13)
- # yada (25)
Has anyone compared performance of transactors comparing backend storages such as Cassandra vs DynamoDB?
should datomic strings always be utf8? We’re seeing umlauts like ü
come out as ?
after transacting them and reading them again…
same is true when importing from an utf8 encoded postgres table. I’ve read recent jdbc drivers should pick up the encoding automatically.
maybe there’s also something with pedestal that we’re missing and it’s all correct in datomic… We are setting the charset=utf-8 in the Content-Type header though
@mkvlr In a scenario involving a peer encoding is not an issue since strings are shared in a type-safe way. Your problem is at some higher layer
(the datomic data in postgres is stored as a blob--it is opaque to the sql server so things like column encoding don't matter)
@favila yes, that’s true for the datomic side, but we’re migrating our data from actual postgres tables into datomic using a script called from the repl
if you see bad characters, then the problem is with what prepared the string for transacting
@favila hmm, on staging (through telnet) I only see ?
, locally it works, alright, so it’s not datomic, thanks! 🙏
user=> (Charset/defaultCharset)
CompilerException java.lang.RuntimeException: No such namespace: Charset, compiling:(NO_SOURCE_PATH:1:1)
user=> (java.nio.charset.Charset/defaultCharset)
#object[sun.nio.cs.US_ASCII 0x56a76e18 "US-ASCII"]
to just alter default encoding I think starting java with -Dfile.encoding=UTF-8
will do