playing with a potential new api using maps (inspired by honeysql)
updating AST generation (allows building queries using maps), it is a bit cleaner and gives more freedom when building a public api, it is slower though. I am not sure if I will ever merge that. Also note the current public facing api is horrible and would be updated if it's ever used.

Ex:
{:select :*, :from :foo, :order-by ([:bar :desc])}
{:update :foo, :set-columns {:bar 1, :baz [+ 2]}}
{:insert :foo, :values {a b, c d}, :using {:timestamp 100000, :ttl 200000}}
use positinal record constructor
split the public api in multiple ns
remove perf tests
update dsl to match v1 of api
improve performance
handle both :columns key and :delete/:select keys for col selection)
kill useless fn
naming
ast and dsl matching
show the use of maps
bump for new release