Fixes #99 by clarifying column names in the readme
This commit is contained in:
parent
94601ee5ae
commit
4fbf69e59e
2 changed files with 3 additions and 0 deletions
|
|
@ -1,6 +1,7 @@
|
||||||
## Changes coming in 0.9.7
|
## Changes coming in 0.9.7
|
||||||
|
|
||||||
* Fix #248 by treating alias as "not a subquery" when generating SQL for it. (@seancorfield)
|
* Fix #248 by treating alias as "not a subquery" when generating SQL for it. (@seancorfield)
|
||||||
|
* Fix #99 by adding a note to the first use of `select` in the README that column names can be keywords or symbols but not strings.
|
||||||
|
|
||||||
## 0.9.6
|
## 0.9.6
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -37,6 +37,8 @@ Everything is built on top of maps representing SQL queries:
|
||||||
:where [:= :f.a "baz"]})
|
:where [:= :f.a "baz"]})
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Column names can be provided as keywords or symbols (but not strings -- HoneySQL treats strings as values that should be lifted out of the SQL as parameters).
|
||||||
|
|
||||||
`format` turns maps into `clojure.java.jdbc`-compatible, parameterized SQL:
|
`format` turns maps into `clojure.java.jdbc`-compatible, parameterized SQL:
|
||||||
|
|
||||||
```clojure
|
```clojure
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue