@dpsutton: re: simple-query — that’s a pretty old version of java.jdbc (0.4.2)… the API has changed quite a bit since then… You mind find folks running into conflicts if they’re on a more recent version in their code already.

(although now I look at your code it looks like you don’t expose any options or anything beyond using java.jdbc/query so you will likely be fine)

ah. thanks so much sean

i'll bump that

Given how query works, you could just pass ~db directly without using with-db-connection — any reason you used the latter?

stack overflow lol

when first getting into clojure looked up how do sql server

so i could sneak it into work

it's really worked out well. we've built a whole reporting website for a rewrite that we are building

Nice! Always glad to see someone using java.jdbc heavily 🙂

are you a dev of that by any chance?

Yeah, I’m the primary maintainer.

oh wow. well thank you very much

its been really straightforward and nice to use

I ported it from the old monolithic contrib back in 2011...

also super nice to be able to use a lisp in a .NET shop

It’s gone through several API rewrites since then

We use it with MySQL at World Singles — supporting millions of queries/updates/etc every day.

i see you use 0.6.2-alpha2 as the current release. Is it standard for a production release to be an alpha?

But I test it with MS SQL Server, with both the MS Type 4 driver and the jtds driver.

is there a "stable" version i should leave it on so people feel safe?

0.6.1 is the stable version

0.6.2 only really has optional clojure.spec support in it

I've seen people say to use the MS Type 4 driver but i've got the 3 in there (I think) and it has worked out well

this allows me to retrieve from clojars rather than require distribution i believe

but i'm not aware of any differenes

Well, the few other minor things in 0.6.2-alpha1 compared to 0.6.1 https://github.com/clojure/java.jdbc/blob/master/CHANGES.md

The new feature we’re starting to use heavily is :qualifier so we can produce namespace-qualified keys directly from a query...

oh i'm interested in that

But, yeah, any version I release is likely already in heavy production use at work.

i'm not sure how common it is but i built a little function to remove the prefixes of column names

at work all of our tables have table names prepended on it

Many of the changes since 0.2.x have been driven by what we need at World Singles.

happen to have anything like that built in?

Well, you could use :identifiers to specify a function to rename columns as they’re turned into keywords.

The default is just clojure.string/lower-case but you could pass any function that, given a string, produces a new string (then the library turns it into a keyword).

oh ok. i'll look into that.

thanks for the heads up

So a variant of your remove-prefix would work:

(defn remove-prefix [prefix]
  (fn [s] (clojure.string/replace s (re-pattern (str "^" prefix)) "")))
(java.jdbc/query db-spec ["select * from sometable"]
         {:identifiers (remove-prefix "sometable")})

Something like that...

(and your first of the result set could be (query ~db [~sql ~@params] {:result-set-fn first}), just FYI)

@seancorfield: is it possible to do Oracle stored procedures calls with java.jdbc? (don't ask why I want it, it's not my choice :)

hey man, i'm working with ms sql server. we all got bills to pay

If you can call them via SQL, yes, it should be possible. There’s no special support for stored procs (yet).

There’s an open issue in JIRA for it http://dev.clojure.org/jira/browse/JDBC-48

seeing the syntax it almost removes the necessity for the macros. didn't realize it could be so succinct

thanks, yep, that 48 exactly I was thinking about

@dpsutton: We have a lot of places where we just call (query db-spec ["select * from …" p1 p2]) and that’s it.

yeah. our reporting tool is basically just a read only display some tables and do some manipulations

didn't know your library had that style syntax. I was thinking it required the jdbc/with-db-connection .... stuff

@sgdread: The main obstacle to JDBC-48 is that I just don’t have any exposure to stored procs so I’m not confident about being able to design/test the feature properly 🙂

@dpsutton: You only need with-db-connection if you want to get a connection and reuse it across multiple statements, otherwise it’s automatic.

And we use a connection pooling library (c3p0) anyway so it’s low overhead to get & close a "connection" on every single query.

well sean, you run a nice project there, great documentation, and you are super helpful on slack. thanks so much

Always looking for feedback to make it better!

i'll keep that in mind

but it looks like my principal issue i was working around was nonexistant

ps, i found the result that led me into that pattern

http://stackoverflow.com/questions/6330688/connecting-to-microsoft-sql-server-using-clojure

it might be nice if there was some article, blogpost, whatever that could replace that at the top of google

especially since jdbc is so nice to use

@seancorfield: If you're interested in test cases, I might get some samples of Oracle sprocs with parameters binding. I also know how to deal with them in Java and can share some samples. Oracle has express edition of the database.

Is there a Docker image I can easily use? That's how I test Postgres. I can't realistically install Oracle on any of my machines here.

Eh, need to do a research on docker. Might be a good idea to use them myself.

@dpsutton: Hard to compete with SO on Google scores...

yeah. shame its old and out of date

sean, have you every used vagrant?

it makes it really easy to create, provision, use, and then destroy vm's

vagrant is awesome

we use it heavily along with ansible

you could create a provisioning script that loads up oracle, exposes some ports and then you can hit it from your normal machine

then vagrant destroy wipes that thing away, but the provisioning script is still alive

I actually have some scripts for oracle provisioning in vagrant

best thing is that these scripts can be checked in. So you could have a subfolder in jdbc with vagrant files for machines with different db types and a standard database schema/ some data

and then run jdbc against them

@dpsutton: I kind of skipped Vagrant and went straight to Docker 🙂

i started on vagrant but work in .NET so i haven't had the pleasure of docker

did vagrant so that all of my school projects still have a version controled environment next to the code

With that SO I downvoted the older answer and upvoted the newer one so at least the outdated version will be lower.

smalltalk, scheme, whatever, they can all still boot up

I'll try to find time tomorrow to edit that answer to make it more up to date and simpler (it's way more complex than it needs to be!).

(added to OneNote!)

Our stack has a lot of moving parts so Dockerizing it really helps. To run our stack locally you need: MySQL, MongoDB, Discovery (a search engine), Redis, Tomcat, and multiple standalone Clojure apps that all communicate...

that sounds super fun

being genuine

We'll be adding DynamoDB to that mix soon. Docker makes that possible without having developers installing, configuring, and running it all individually.

the worst thing to ever hear: "well it works for me"

And we're also the crazy company that has a lot of ColdFusion code and we run Clojure inside that 🙂

haha. i've never touched it. can't imagine how the two go together

I built a bridge library back in 2011 and it's core to our platform...

youre a talented guy sean

i need these two environments to work together. Sean: I got you

jdbc is depcrated. Sean: I got you

Hahaha 🙂

FYI, ColdFusion calling Clojure https://github.com/seancorfield/datamapper/blob/master/Service.cfc#L70-L77

(modern CFML looks like JS -- the WS "object" is actually a Clojure namespace so WS.data.find_by_keys( name, args, orderBy ) is really just (WS.data/find-by-keys name args orderBy)

is there already a java interop so that this isn't as crazy as it seems or did you really build some crazy stuff here?

The "magic" code relies on two key things: Clojure's Java API and CFML onMissingMethod() so we can call "non-existent" methods and it re-routes them through a .invoke() call.

There's some rather terrifying stuff behind the scenes: https://github.com/framework-one/fw1/blob/develop/framework/cfmljure.cfc

oh it runs on the jvm. I didn't know anything about it so i thought you were reaching across some really crazy boundaries

CFML compiles on-demand to JVM bytecode (just like Clojure). Has done for about 15 years.

Prior to that it was interpreted (the interpreter was written in C++ for five years earlier).

just really knew the name

looking over fw1, that looks like there was some fun stuff

and then i'll bet you were really really done with it but still had edge cases

nice work

There's a Clojure version of FW/1 too: https://github.com/framework-one/fw1-clj

We use for some web apps that are pure Clojure

i'm looking through your engine library. that seems quite nice

It requires discipline to use, but we like what it's making us do... I blogged about it recently...

http://seancorfield.github.io/blog/2016/07/18/start-your-engine/

does this require you to parse sql?

oh nevermind

i thought you were running the sql against the :ram object

No, query is based on a protocol and there's an implementation using java.jdbc

And an implementation extended to hash maps as well 🙂

yeah. for some reason i was thinking that it knew you did updates which hadn't ocmmited yet so it queried the ram instead of the underlying db

very nice (re hash maps)

The nice thing about the idiom is that it extends to things like message queues, email systems, generator processes etc

At World Singles we have Committable data stores that implement all sorts of things... and Queryable data stores for all sorts of stuff too

very cool

yeah i can imagine data access is your bread and butter

i've got to head out. you were super helpful and interesting. thanks

Any time. Feel free to DM me if you ever have java.jdbc Qs

Is there a take-last that returns the individual items I'm looking for wrapped in a vector?

(vec (take-last n coll))

no, like

Say I'm running through a log

take-last gives me (x line y line z line)

vec take-last [x line y line z line]

i'm looking for ([x line] [y line] [z line])

modding take-last doesnt look like itd be trivial either

(map vec (partition 2 (take-last X coll)))

why partition 2?

oh

the nil

right

to break your collection up into subcollections of 2 items each

why 2 items?

> (map vec (partition 2 (take-last 4 [1 2 3 4 5 6]))) ;; ([3 4] [5 6])

oh, i get it

i meant

([line] [line] [line])

my mistake

your solution did work though, thanks!

> (map vec (partition 1 (take-last 4 [1 2 3 4 5 6]))) ;; ([3] [4] [5] [6]) 😁

exactly

sequence function composition ftw

god bless fp

bit of an addiction, tbh

agreed

I'll turn my workplace into a clojure shop just yet hehehehe

in the partition 1 case you can simplify it to > (map vector (take-last 4 [1 2 3 4 5 6]))

and if your input is a vector, it would be better to use subvec: (mapv vector (subvec [1 2 3 4 5 6] (- (count [1 2 3 4 5 6]) 4)))

Is anyone developing in a docker container using emacs and cider? If so, are you able to jump to fn definitions in a different ns? I keep getting no source locations and https://github.com/clojure-emacs/cider/issues/589 doesnt' seem to address it for me

recommend asking in #C0617A8PQ as well, @petr

Hah! Good to see you Rob

any ideas why I wouldn't be able to iterate through that vector?

I'm trying to run it through a map but nothing's really happening

(map (fn [ln] (println ln)) line-list)

@nnbosko: map is lazy

doall then

is for lazy too? it was also failing with that

Yes

I use (into [] <lazy-seq>) a lot

there should be a flag for non-lazy mapping

Or just use mapv

well yes

and now it seems to get stuck at the last result and stay put forever, boy am I having trouble today

that's what I get for not changing the text processing function as well, got it.

Is there a recommended plugin for lein that will generate dockerfiles? I’ve looked at the palletops one, lein-uberimage, but it seems to be abandoned.

alexmiller: I was in here asking about an issue with transit-clj a few days ago; I opened an issue there, but now I’m wondering if that should be on transit-java instead? (https://github.com/cognitect/transit-clj/issues/33)

Since transit-clj appears to pretty much be wrapping transit-java

and I think the issue is in the version of org.msgpack/msgpack that transit-java is using

I don’t know that it matters much which of those it was filed on

(using signed bytes, I think)

interesting if it’s a version issue - why do you think so?

the newer version of msgpack seems to be doing the reading of bytes in a difference way

haven’t had a chance to test it yet though

https://github.com/msgpack/msgpack-java/blob/develop/RELEASE_NOTES.md

anything there look relevant?

actually, maybe that’s not the right lib

oh, it isn’t?

I think the package name changed at some point, from org.msgpack/msgpack to org.msgpack/msgpack-core

I guess it is - it’s a little confusing but looks like that lib has artifact-id msgpack, so that’s right

transit-java is using 0.6.10

https://github.com/msgpack/msgpack-java/issues/213

looks related - that was fixed in 0.6.11

yeah, exactly that

no, 0.6.12

that is precisely the issue

I’m a big fan of existing fixes to thorny problems :)

Indeed!

so that gives you a workaround - exclude the dep and add your own msgpack version

I’ll prod someone about updating and verifying transit-java

excellent; for now I’ve just been making sure the strings are < 127 or > 255 bytes 😛

thank you!

I feel like I'm missing something really obvious here:

(defn f [& {:keys [a b c] :as args}]
  (println a b c))

(defn g [& {:keys [a b c] :as args}]
  ;; do some stuff & then pass args on to f
  (f args))

Remove the & from the arglist if you want it to take a single argument.

Hmm. Less convenient for anyone calling it directly, though.

(as a subjective matter of taste)

maybe try a true multi-arity setup rather than the optional parameters?

@dpsutton: I don't love that option, because I want it to be easy for people to omit any subset of params.

optional parameters and destructuring rest arguments have become quite unpopular for their lack of composability.

I still like 'em 🙂. But definitely awkward in this case.

wait, is args optional or not?

if it is, i don't see why you don't want a 0-arity version

if its not optional, remove the & as mentioned earlier

eggsyntax: maybe you should use common lisp instead, for it's excessive lambda list madness. there you get all you want and more in argument list specification 🙂

@dpsutton: Not sure I understand what you're saying. Desired calling convention is like (g :a 2 :c 3) (or any variant thereof).

@hans: fair enough, that would certainly be a solution 😉

oh i'm with you now

yeah. common lisp has a nice way of setting defaults i believe

eggsyntax: if you stick with clojure, though, i can really suggest that you forget about believing that it has keyword arguments

I'm just used to clj destructuring being so rich that it surprised me there isn't an obvious way to do it. But sounds like there's not.

i was misreading destructuring keys from an object, not from a rest type

dpsutton: not only that, but you can also determine whether a certain keyword has been specified or defaulted.

yeah. are you against making a map and merging with a notion of default?

dpsutton: and you can rename the variable that the argument is bound to

I do miss Python's handling of optional args; it's one of the few things I miss in Clojure.

really, common lisp lambda lists are something to drool about.

sorry for OT

i'm in .Net land at work and optional stuff is really nice as well

@dpsutton: nah, that'd work too 🙂

but i agree with you now that it's not as nice syntax

@eggsyntax: You can provide default values in the destructured arg with :or.

exupero: which is workable, but fugly

^ agreed.

(note on the Python version: it was great for the common case, but had a deeply ugly pitfall: defaults were set at function definition time, which meant that if the default value was an array or other mutable object, changes to it would persist across function calls.)

cf https://stackoverflow.com/questions/1132941/least-astonishment-in-python-the-mutable-default-argument

Which is the most reliable SMTP server one can use? I found https://github.com/whilo/bote which is kind of interesting, it uses SubEtha SMTP

why not use subethasmtp directly?

bote doesn't seem to give you much of anything

subethasmtp is good

yeah @hiredman I think you are kind of right

I found an odd behavior, maybe it is expected, but just wanted a confirmation if anyone know

(every? true? nil) ;=>> true (every? true? [nil]) ;=>> false

Clojure 1.9.0-master-SNAPSHOT
user=> (every? true? [nil])
false
user=>

the first line is odd and I just found out a test was passing but it shouldn't have

sorry I corrected above

every? is always true on an empty collection

http://stackoverflow.com/a/17461741

oh right...it is the old story of an AND when no items are tested? There is an example actually here: http://clojuredocs.org/clojure.core/every_q

yeah I was kind of forgetting that

it is a 101/interview question 😄

I hope I'm not asked questions like that in interviews

well, I have made my gaffe of the year, I can now retire 😄

Sometimes I find it helpful to mentally translate to: “there is no item in coll which does not satisfy pred."

I actually had an interview yesterday and one of the questions was why in Java (Integer.valueOf(-128) == Integer.valueOf(-128)) is true (I answered that it should be false)

but ok that's not a logic question

it is a side effecting Java quirk of caching objects for number within some range

ah that's because integers are objects and the common ones are created at start up but when you ask for ones outside of a small core range they are newed so to speak? And the == test here is using reference equality?

is there a common term for things that manage resources that can have multiple users and dispose them when there's no user left?

Pools

Yeah Python has that behavior for boxed integers as well. All the boxed integers are singletons, and the ones in a small range around 0 never get GC'd.

Interning, I think?

The Java cached primitives are never disposed

It's actually mandated in the spec

Can someone explain to me if such a question in an interview has any value (no pun intended) ?

@lprefontaine: creating quality tech interview questions is a difficult thing because most are subjective and on a job you could look it up. But I agree that it seems particularly and purposefully obscure to try to have the (maybe stressed) interviewee identify that you’re comparing two objects using == and then also knowing about Java caching certain numbers

@alexmiller: yes it is in the specs, I did not know that

didn't want to open a flame as I guess we all have our idea on what to ask in interviews, the interviewers were actually superfriendly and wanted to go in deep but always smiling and knowing that these things are kind of...well...imho worthless

In my world I deliver value. The fact that an implementation has such quirks is irrelevant to what I can deliver. The industry seems to be in such a disarray to select candidates that I am not surprised of its lack of throughput if this is the kind of discriminant factor it's using to select 'the best candidate's. I would have left the interview at the first question of this kind. Everyone should. This world is sick.

at least now they know that I did not read the Java spec, for them is worth knowing that

btw I got an offer

so the interview went well

because it is clear maybe that you can go deep, but also clear that you cannot know everything

ouf, 😂

which is healthy

Congratulations on that. And yes, I feel like it’s probably also a benefit to know someone didn’t just spend their free time reading the Java spec for no particular reason

I would rather read some byte code on a sheet of toilet paper 😬

^ many lol (it is a Java job so now I dunno what to do, other flame open :D)

have a nice start on your new job, I'll get back to my clojure/jdbc/oracle/unfamiliar schema problem...