This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-18
Channels
- # admin-announcements (3)
- # alda (1)
- # boot (85)
- # capetown (4)
- # cider (10)
- # clara (16)
- # cljsrn (3)
- # clojars (35)
- # clojure (83)
- # clojure-austin (8)
- # clojure-brasil (4)
- # clojure-canada (16)
- # clojure-greece (2)
- # clojure-ireland (7)
- # clojure-russia (23)
- # clojure-spec (22)
- # clojure-uk (151)
- # clojurescript (97)
- # core-async (10)
- # cursive (1)
- # datascript (7)
- # datomic (21)
- # defnpodcast (13)
- # devcards (3)
- # emacs (4)
- # events (3)
- # hoplon (18)
- # juxt (4)
- # leiningen (7)
- # mount (4)
- # off-topic (2)
- # om (1)
- # onyx (30)
- # planck (6)
- # proton (81)
- # re-frame (3)
- # reagent (9)
- # rum (10)
- # spacemacs (1)
- # specter (6)
- # testing (7)
- # untangled (66)
- # vim (84)
- # yada (23)
I’m using SQLite :memory:
databases, since I want the database to be totally fresh for every test so every test does (joplin/migrate-db {:db {:type :jdbc :url “jdbc:sqlite::memory:” …)
before running the test but I’m getting an SQL exception about the ragtime_migrations
table not existing.
Mmm, thinking about this it’s probably because something doesn’t hold onto the connection long enough, so between two calls there’s a totally new database.
I think the difficulty here is that joplin only wants a URL and every time something attempts to open the URL jdbc:sqlite::memory:
it will get a totally new database, since I can’t pass my connection object into the target map to migrate-db
I don’t know how to stop this from happening.