The basic principle is the same, but the api is a little different, 
especially after YeSQL 0.5.

The biggest things for me:
- HugSQL allows you to replace jdbc-backend (which is what allows my async 
package). YeSQL is hardcoded to clojure.java.jdbc
- HugSQL allows you to specify if one or many values are returned from a 
query, in YeSQL, a list is always returned.
- YeSQL differentiates commands based on name convention (transactions has 
names that end with !), in HugSQL you configure it in the sql file.
- YeSQL takes options (with db) as the last argument to a 
query/transaction. HugSQL takes the db(!) as the first argument.
- HugSQL is easier to use with stuart sierra's component library due to 
previous statement.
- HugSQL is easier to use with jdbc-transactions due to the same reason 
(don't have to wrap/unwrap db from YeSQL options).
- HugSQL is more flexible, as it allows different quoting and insertion 
strategies, allowing you to create more flexible SQL functions.

onsdag 4. november 2015 18.42.30 UTC+1 skrev chepprey følgende:
>
> Is there anything that compares/contrasts HugSQL and YesQL?
>
> On Sunday, October 25, 2015 at 9:36:40 PM UTC-4, Robin Heggelund Hansen 
> wrote:
>>
>> You can now have async communication with your postgres database and 
>> HugSQL over plain core.async channels.
>>
>> https://github.com/Skinney/hugsql-async
>>
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to