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

Add next.jdbc plan to the api #30

Open
arichiardi opened this issue Mar 31, 2021 · 2 comments
Open

Add next.jdbc plan to the api #30

arichiardi opened this issue Mar 31, 2021 · 2 comments

Comments

@arichiardi
Copy link

The library expose a way to use transducers when transforming result sets: a function called plan.
This is very handy and one of the main features of next.jdbc.

Describe the solution you'd like
Add next.jdbc/plan to the api. There might be a bit of spelunking because of the implementation but it might doable.

Describe alternatives you've considered
Post process results sets.

@borkdude
Copy link
Collaborator

I'm afraid this isn't possible due to the nature of pods, unless you can provide a string/EDN version of the function that should be applied to the result set. Would that be a reasonable compromise?

@arichiardi
Copy link
Author

I personally like how zprint does it - basically you specify a function in its .edn file

https://github.com/kkinnear/zprint/blob/master/doc/options/optionfns.md

This could be added to bb.edn with some kind of keyword wrapping it or something...not sure...it can be an extension mechanism for contributing to pods

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants