This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-02
Channels
- # announcements (13)
- # architecture (18)
- # babashka (90)
- # beginners (80)
- # calva (35)
- # chlorine-clover (29)
- # cider (24)
- # clj-kondo (4)
- # cljfx (3)
- # clojure (60)
- # clojure-australia (2)
- # clojure-europe (60)
- # clojure-france (2)
- # clojure-germany (3)
- # clojure-italy (4)
- # clojure-nl (84)
- # clojure-norway (7)
- # clojure-uk (53)
- # clojurescript (54)
- # clojureverse-ops (1)
- # community-development (6)
- # conjure (1)
- # contributions-welcome (1)
- # cursive (12)
- # datomic (1)
- # fulcro (16)
- # garden (61)
- # girouette (1)
- # graalvm (14)
- # hugsql (1)
- # instaparse (5)
- # jobs-discuss (11)
- # keechma (1)
- # lambdaisland (3)
- # off-topic (20)
- # pathom (1)
- # re-frame (3)
- # reitit (2)
- # releases (1)
- # remote-jobs (2)
- # reveal (11)
- # shadow-cljs (58)
- # spacemacs (5)
- # sql (3)
- # startup-in-a-month (1)
- # vim (2)
This nice article was in HN homepage recently https://www.commandprompt.com/blog/null-characters-workarounds-arent-good-enough/ would you find it a good idea to have a middleware-like piece of code that stripped out ascii NUL chars?
might be cleaner to use Spec/Malli/etc in an earlier layer :thinking_face:
e.g. (spec/def ::str (spec/and string? (complement has-null-chars?)))
and use it as a vanilla validation along all other app-level validations
I see it's a PostgreSQL-only problem, according to that article. I started reading it and I'm thinking "Really? I've never encountered this as a problem with any database!" but then I've never used PostgreSQL 🙂