Closed kelvinqian00 closed 3 years ago
Thanks! Fix on develop. I'll probably cut a new release over the weekend with this fix.
Cool. However, I saw that you forgot to make :property-separator
a keyword on this line: https://github.com/seancorfield/next-jdbc/blob/cc975f825dd9ee2993c43114b8f9454d00616feb/src/next/jdbc/connection.clj#L166
Ouch! Good catch, thank you! Glad I didn't get time to cut a new release with that bug still in it. Fixed on develop.
Version 1.2.709 is available with this fix.
When constructing a JDBC URL for H2 using
next.jdbc.connection/jdbc-url
, the resulting URL uses the incorrect property separator, namely colons instead of ampersands. (H2 doc reference)In addition, adding the
:property-separator
key to the param map adds an extraneousproperty-separator
query param to the URL.Code:
Expected:
Actual:
And this is the result when I add the kv-pair
:property-separator ";"
to the param map: