Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Korma query to jdbc conversion Wrong number of args #362

Open
ghost opened this issue Jul 29, 2016 · 5 comments
Open

Korma query to jdbc conversion Wrong number of args #362

ghost opened this issue Jul 29, 2016 · 5 comments
Labels
inactive-issue? This issue should be closed within 2 weeks of the most recent comment due to inactivity

Comments

@ghost
Copy link

ghost commented Jul 29, 2016

I'm trying to do simple queries like select or insert.. It is a mysql database.

When I try to do something simple like a select * from users
(select users)

I get:

ArityException Wrong number of args (4) passed to: jdbc/query clojure.lang.AFn.throwArity (AFn.java:429)

dry run :: SELECT users.id, users.username, users.password, users.first_name, users.last_name, users.title FROM users :: []

Why does ::[] get generated I believe this is causing the issue.

@immoh
Copy link
Member

immoh commented Jul 31, 2016

I believe you are using a newer version of clojure/java.jdbc that is not compatible with the latest release of Korma. Check the README how to pin it to a version that works with Korma.

@ghost
Copy link
Author

ghost commented Aug 1, 2016

I'm using [org.clojure/java.jdbc "0.3.7"]

@immoh
Copy link
Member

immoh commented Aug 1, 2016

Are you sure you don't have newer versio of org.clojure/java.jdbc on classpath? I cannot reproduce this based on this information.

:: [] in the end of logging means there are no query parameters, it is certainly not causing this.

@lukehharris
Copy link

btw I had the same issue, making sure i was using the correct versions solved it

@venantius
Copy link
Contributor

I'm going through old issues and trying to clean them up. Has this issue persisted?

If there hasn't been a response to this issue in 2 weeks, I'll close the ticket.

@venantius venantius added the inactive-issue? This issue should be closed within 2 weeks of the most recent comment due to inactivity label Feb 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inactive-issue? This issue should be closed within 2 weeks of the most recent comment due to inactivity
Projects
None yet
Development

No branches or pull requests

3 participants