-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Support citext
#104
Comments
@cortopy I rely on https://github.com/SeaQL/sea-orm to generate the entities. After a quick look I found it is related to this file https://github.com/SeaQL/sea-orm/blob/master/sea-orm-codegen/src/entity/transformer.rs#L62 |
Hey @cortopy, could you illustrate the use case of |
@billy1624 it is a plugin for PostgreSQL, that provides a new data type @cortopy do not mind to tell me if I am wrong. |
@karatakis that's exactly it. The Seaography currently thinks that I've been looking a bit more on seaorm and I think the issue also stems from the limited support there for user types. It seems that only So anybody using any other type will get an enum generated that is just not right. |
Can we represent |
I'd say so yes |
Alright, then it's more related to sea-schema. SeaQL/sea-schema#89 |
I've managed to support |
This issue is not present in #114, wait for 1.0.0 release :) |
Motivation
citext
is a popular extension and when enabled, seaography thinks it's an enum an generates invalid codeProposed Solutions
Recognise that
citext
is pretty much likeText
for all purposes that matter for client code. Maybe just an alias?Additional Information
This is the code generated, which is wrong:
sqlx doesn't support
citext
easily either as per launchbadge/sqlx#295. However, I don't know if seaorm/seaography could do something about itThe text was updated successfully, but these errors were encountered: