Sean Corfield writes:
>> The required steps to setup streaming are different from database to
>> database and I guess they may change with the driver version being used.
>
> This is really the crux of the problem here – I’m not sure what java.jdbc can
> do generically to make this much easier.
You'll let me know if I should be looking elsewhere, before asking here
but, can I move and resize panes?
Each pane defaults to full-height, shared-width. I would like my repl pane
to be a short, full-width pane, across the bottom of my screen.
Can I do that and, again, is there a go to place
I'm pretty sure you can just drag the pane out left and to the bottom to move
it. And you can resize the height by hovering the mouse at the edge.
Those questions I think are best answered here: https://discuss.atom.io
--
You received this message because you are subscribed to the Google
Groups
Rather than doing something that requires a dependency on specific JDBC driver
classes, it seems that if an :auto-commit option in the db-spec were honored by
get-connection you would get what you needed:
(into [] (take 2) (jdbc/reducible-query (assoc config/db :auto-commit
false) query
I've been meaning to chime in here …
My take is that clojure.java.jdbc should not be responsible for providing
options to the driver to guarantee streaming lazy results, as much as I
understand how convenient that would be for users of the framework. It should
of course support passing all of
Yes, I agree that java.jdbc should not try to cater to various DBs/drivers’
quirks in terms of exactly what incantations you need to murmur in order to
achieve a specific behavior. I do believe, however, that it should go out of
its way to make sure you can murmur those incantations via java.jdb
Sean Corfield writes:
> Rather than doing something that requires a dependency on specific JDBC
> driver classes, it seems that if an :auto-commit option in the db-spec were
> honored by get-connection you would get what you needed:
>
> (into [] (take 2) (jdbc/reducible-query (assoc confi
> In my case config/db is really read from a config.edn file and may point
> to a mysql, postgresql or sqlite database.
Then you can add a :streaming-options key to your EDN file and do this in your
code:
(into [] (take 2) (jdbc/reducible-query config/db (:streaming-options
config/db)))
Yes, I agree that java.jdbc should not try to cater to various DBs/drivers’
quirks in terms of exactly what incantations you need to murmur in order to
achieve a specific behavior. I do believe, however, that it should go out of
its way to make sure you can murmur those incantations via java.jdb
