-
-
Notifications
You must be signed in to change notification settings - Fork 320
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
Implementation for email data type #245
Comments
Note that this is already implemented at the DB level, and reflects properly in SQLAlchemy. We just need to make it possible to work with from the Column API and have some agreement about how the type should be represented in the API. (I.e., varchar is shown as Do we want to continue using the DB name for the types in the API, or come up with some kind of mapping to make them look better in the API? One detail is that if in the dim future we supported a different DB backend, the DB names even for some of the non-custom types would potentially change in the API. |
I know some of this is already implemented, but I wanted to make a full checklist of what we need for this type to work properly. I'll make a separate ticket for mapping types to the API, I think we'll need some way to map DB types to more human-friendly types. |
Closing this since all subtasks are done. |
Problem
Users may want to store emails in their database and utilize functionality that is specific to email addresses such as validation and grouping. We should allow them to do so and implement this type appropriately in the backend.
Proposed solution
PostgreSQL does not have a built-in type to handle email addresses, so we will create a custom type that users can install if they want to use it.
Tasks that need to completed:
Additional context
The text was updated successfully, but these errors were encountered: