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

uuid AutoKey? #52

Open
imalsogreg opened this issue Nov 9, 2015 · 3 comments
Open

uuid AutoKey? #52

imalsogreg opened this issue Nov 9, 2015 · 3 comments

Comments

@imalsogreg
Copy link
Contributor

I like how TH-derived automatically incremented int keys free me from having to put any kind of primary key directly in my type, since often the key has nothing to do with my business logic, and sometimes I don't know what the key is until the database tells me.

Is it possible to get the same functionality but with V4 UUID's (if I commit myself to Postgres)? Or would I need to have an actual UUID field in my Haskell record if I want a UUID key?

@lykahb
Copy link
Owner

lykahb commented Nov 17, 2015

I think it will be a nice feature. I will see if there is a way to replace AutoKeyType used for the autoincremented keys with something more flexible. If the primary key can be defined with custom database type and a default, that would be sufficient for using UUID.

@taylor1791
Copy link

Any progress or thoughts on this?

@lykahb
Copy link
Owner

lykahb commented Jan 14, 2016

Some parts of the architecture rely on the autoincremented key always having the type defined for the database in the type family AutoKeyType. Adding setting for the DB schema is only a half of the feature. I'll try to get back to this issue the next week.

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

3 participants