Feel free to create a JIRA issue against clojure.java.jdbc if you want me to dig into this -- I'm surprised the difference is quite that big.

ok 🙂

(I'm up to my neck in work stuff right now, but can take a good look at it later in the week)

If you can also give an idea of how many rows you're working with in the ticket, then I can create a repro case to test it with timings.

with this table there are only 1500 rows

How can I use cursor with MySQL to avoid full table load?

or how I can process every row w/o loading them all in one go? I tried approach from here http://clojure-doc.org/articles/ecosystem/java_jdbc/using_sql.html - but it loads all records

please help

@seancorfield could you please help with this?

I remember reducible-query being a thing for that @kirill.salykin , but I’m not 100% sure...

@kirill.salykin You'll need to tell us what you've actually tried, exactly, in code -- that page has a lot of code on it! Also, you may need specific parameters and settings to make it work with MySQL -- PostgreSQL was where others have confirmed this works, but that required an enhancement to java.jdbc to make it work (the ability to set connections to readonly and not autocommit). MySQL may require those or similar options. Finally, it's a bit rude to @ someone who is not currently engaged in ongoing channel discussions: the @ mention can cause an alert to be sent to their phone and you did that in the middle of the night 😐

Fyi you can setup "do not disturb" for a range of hours, it's quite handy

I do that on most slacks (work included), critical stuff requires an sms

If anyone here wants to try Zulip -- an open source service with unlimited search history -- there's a SQL stream here https://clojurians.zulipchat.com/#narrow/stream/152063-sql -- I'm happy to provide support in both venues.

can anyone point me in the right direction on why jdbc/set-db-rollback-only is committing transactions instead of rolling them back? I have code that looks like this:

(defn atomic-queries
  [test-fn]
  (jdbc/with-db-transaction [tx sys/db]
    (jdbc/db-set-rollback-only! tx)
    (binding [*txn* tx]
      (test-fn))))

(deftest notes-for-user
  (is (= {:id 1} (notes/create-note *txn* "cody"))
      (= {:id 2} (notes/create-note *txn* "cody"))))

the first time I run it it succeeds, and subsequent times it fails since the returned ids are incrementing

@ccann What does your create-note function look like?

i’m using HugSQL so it’s wrapping some sql:

(defn create-note
  [db user-id ref-id svg-file]
  (insert-one db {:user-id user-id
                  :ref-id  ref-id
                  :svg     (.getBytes svg-file)}))

-- :name insert-one :returning-execute :1
-- :doc Insert one Note
INSERT INTO notes (svg, reference_id, user_id)
VALUES (:svg, :ref-id, :user-id)
RETURNING id;

And I assume you're setting atomic-queries as a fixture for clojure.test?

I wonder if something insert-one is doing under the hood is messing with the transaction information?

(I haven't used HugSQL)