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

Configuring row normalization #36

Open
hrach opened this issue Oct 25, 2014 · 5 comments · May be fixed by #138
Open

Configuring row normalization #36

hrach opened this issue Oct 25, 2014 · 5 comments · May be fixed by #138

Comments

@hrach
Copy link
Contributor

hrach commented Oct 25, 2014

Would be nice to have confirugable normalization of database row result.
Currently, it's impossible to add own new normalization (like pgarray?). On the other hand, it's impossible to disable some normalization (like all transforms to datetime/dateinterval, ...)

@hrach
Copy link
Contributor Author

hrach commented Oct 25, 2014

Any idea, how api could look? cc @dg

@JanTvrdik
Copy link
Contributor

Does it have to be solved with configuration? Why not just extract to logic from ResultSet to RowNormalizer?

@hrach
Copy link
Contributor Author

hrach commented Oct 25, 2014

Of course, configuratin means just some API :-) The question, how to inject own RowNormalizer into ResultSet.

@JanTvrdik
Copy link
Contributor

Global service for default normalizer injected by constructor to ResultSet + setter on ResultSet for specific behavior on a single result.

Regarding current implementation – why is driver-specific normalization called after general normalization and not before?

@KacerCZ
Copy link

KacerCZ commented Apr 1, 2015

This feature would be great, because sometimes I don't need normalization overhead.
Workaround I use is ResultSet::getPdoStatement()->fetch().

@Unlink Unlink linked a pull request Jun 2, 2016 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants