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

Make it easier to create builders with pluggable naming conventions #30

Closed
seancorfield opened this issue Jun 4, 2019 · 1 comment

Comments

Projects
None yet
1 participant
@seancorfield
Copy link
Owner

commented Jun 4, 2019

See https://clojureverse.org/t/next-jdbc-1-0-0-beta-1/4307/3

It would be nice if there were a generic get-pluggable-column-names that accepted a string-based naming strategy and/or a generic builder that accepted such (and handled the column name strategy directly).

Perhaps then rewrite the lower variants in terms of that?

Need to consider qualified/unqualified variants of it too.

@seancorfield

This comment has been minimized.

Copy link
Owner Author

commented Jun 5, 2019

get-modified-column-names, get-unqualified-modified-column-names, and all the matching as-*-(maps|arrays) variants too.

Rewrote lower variants in terms of those. Also updated next.jdbc.optional builders.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.