Fork me on GitHub
#sql
<
2019-10-03
>
jumar11:10:06

@kulminaator that's an interesting point; so we can view blocking IO (on the DB client side) as a sort of backpressure strategy 🙂. Perhaps it's DB implementations themselves that benefit more from non-blocking operations rather than the DB clients...

dharrigan14:10:09

Ah, much rejoicing, PostgreSQL 12 is out! 🙂

parrot 1
gklijs14:10:49

Anything in particular that's changed/improved?

yogidevbear14:10:56

A work colleague pointed this out: >PostgreSQL 12 introduces the ability to rebuild indexes without blocking writes to an index via the REINDEX CONCURRENTLY command, allowing users to avoid downtime scenarios for lengthy index rebuilds.

Cora23:10:16

is there a way to put a limit on the query generated by find-by-keys?

Cora23:10:22

in next.jdbc, I mean

Cora23:10:09

hmm doesn't seem like it

seancorfield23:10:33

No. The "friendly" functions are intended to be just sugar for very basic operations. Mostly you should use plan, execute-one!, and execute!.

Cora23:10:36

hmmm ok. so for more dynamic stuff I should be looking for a query builder then

seancorfield23:10:51

HoneySQL is great.

Cora23:10:58

cool, I'll give that a shot

Cora23:10:27

how do you close a given next.jdbc connection?

Cora23:10:20

I suppose it depends on if you have a pool or not

Cora23:10:01

ah, just (.close conn)