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 extension types database agnostic (or at least parametric) #22

Open
maurer opened this issue Jan 2, 2017 · 0 comments
Open

Make extension types database agnostic (or at least parametric) #22

maurer opened this issue Jan 2, 2017 · 0 comments
Labels

Comments

@maurer
Copy link
Owner

maurer commented Jan 2, 2017

Right now, dynamically extended types are implemented via the assumption that they are being implemented for postgres. Since for many types (e.g. bitvectors) it may not be plausible to be completely agnostic, since different databases have different representations, it would instead make sense to be parametric on which database is being used. However, this would cause the Holmes handle itself to need to be parametric over which database is in use, which would be unfortunate.

@maurer maurer added the quality label Jan 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant