Hi. We are using Lacinia, Ring, and JDBC wrapped with a connection pool. Anyone have some suggestions for best practices to pass around the wrapped JDBC? Our current workaround is ugly: (def global (atom (c3po...jdbc init...)) and then doing @global inside a resolver fn.

@johnny.martin Pass it in via resolver context.

Thank you--very helpful. We found the optional context argument in the docs, after reading your suggestion. Thanks again!

no problem

noob question: I am using boardgamegeek example with PR patch which calls (start-server) on lein run. Every change i make i need to ctrl+c and lein run again. What is the proper way to dev with this pedestal-server without a complete restart

I'll be looking at what Pedestal offers to support that.

Make it work. Make it right. Make it fast.

@mpenet if your database is generating updates faster than clients can handle it, what other option do you have except for disconnecting the client or dropping updates?

that's why i'm asking what'll be the interface in lacinia for disconnecting from a stream. we're using yada+aleph in front of lacinia

@matthewdaniel I'm not sure about the boardgamegeek example, but when you create a bare pedestal template with lein, it defines a run-dev function

my work flow usually involves starting a repl (`lein repl` or CIDER or what-have-you) and running (def serv (run-dev)), which starts the server, and can then be stopped: (server/stop serv)

so you can do e.g.:

example.server=> (def serv (run-dev))
example.server=> ; make some changes to some files, e.g. example.schema
example.server=> (require example.schema :reload) ; reload the changed file
example.server=> (require example.server :reload)
example.server=> (server/stop serv)
example.server=> (def serv (run-dev))

I simple created a helper function to do all the reloading and restarting, so I can do (def serv (reload-schema serv))

here's an example repo: https://github.com/Lokeh/graphql-demo