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

SQL dialects #6

Closed
e0d opened this issue Aug 22, 2013 · 9 comments
Closed

SQL dialects #6

e0d opened this issue Aug 22, 2013 · 9 comments

Comments

@e0d
Copy link

e0d commented Aug 22, 2013

Interesting project. Is there a a thought a supporting SQL dialects? What DB's have you been targeting so far?

@jkk
Copy link
Collaborator

jkk commented Aug 22, 2013

I've mainly been using it for MySQL and PostgreSQL so far. Supporting other dialects is possible, depending on what in particular is needed -- custom clauses, quoting behavior, etc. Did you have specific requirements in mind?

Note that I'm planning to release another library that sits on top of HoneySQL that provides more advanced features, such as relationship-aware querying and saving.

@fdhenard
Copy link

I've been using korma for a while, but this korma issue caused me to look for another sql abstraction library. I tried honeysql yesterday, and though my honeysql query is not dialect independent, it was easy to get around that issue using the :modifiers clause (I would like it to emit the correct sql server query when using the :limit clause). I can also see how it would be easy to make it dialect independent with little altering of honeysql. Maybe the hooks already exist to do that, but I didn't have time to look into it.

I look forward to keep working with honeysql, and maybe get good enough to contribute at some point. I also look forward to the relationship-aware features you're talking about.

@jkk
Copy link
Collaborator

jkk commented Aug 23, 2013

One way to handle it might be to add new clauses to honeysql, such as :select-top or :offset-fetch and then have the higher-level lib translate any :limit clauses when it detects that MSSQL is being used. The higher-level lib (codename Cantata) is aware of db types but honeysql is mostly not, except when it comes to quoting behavior. As far as honeysql is concerned, it's up to the caller to choose the right clauses.

@fdhenard
Copy link

Does Cantata exist publicly where I can look at it? Also would Cantata merely output honey sql, and then honey will be responsible for outputting to clojure.jdbc queries? Sounds interesting!

@jkk
Copy link
Collaborator

jkk commented Aug 23, 2013

Cantata is not public just yet; planning to release it next week. It keeps track of database and data model stuff, and passes its "higher order" sql-like queries to honeysql for translation to sql, then to clojure.java.jdbc for execution.

@fdhenard
Copy link

Sounds nice!

@theleoborges
Copy link

Hey @jkk ,

I realised cantata is on clojars but the repo doesn't exist. Is this because the project isn't public yet?

@ddellacosta
Copy link
Collaborator

@jkk Can/should we close this one? Seems like it's just a dead comment thread at this point.

@jkk
Copy link
Collaborator

jkk commented Mar 5, 2015

yep

@jkk jkk closed this as completed Mar 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants