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
Improve typecasting in mathesar #3560
Comments
I do think we need to do some serious work on our casting functionality, including how to handle casting to/from types we don't explicitly support. However, I think we should avoid getting too deep into that before the beta. We also need to do some product-level rethinking to figure out how to support this. The reason the current casting functions are somewhat restrictive is to provide a level of safety for the user. In your |
Problem:
mathesar_types
namespace (469 to be exact!!!) we still haven't fully covered all typecasts supported by postgres for the types that mathesar currently supports.Potential solution:
A complelling example:
Type aliases are confusing:
Are we okay with using type names mentioned in pg_type rather than their synonyms in the backend?
(referenced from : https://www.postgresql.org/docs/current/datatype.html)
Getting info about existing typecasting functions provided by postgres:
The text was updated successfully, but these errors were encountered: