-
-
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
Create URI custom type and handle it in the backend. #412
Comments
MATHESAR_URI
custom type and handle it in the backend.
If we can spare the time for implementation, I suggest we implement our own. This would avoid the need for installing a 3rd-party extension which isn't supported everywhere (e.g., on Amazon's RDS instances). |
We might still want to use it to speed up implementation and consider writing our own at a later date. It depends on how much work it is to write our own. We could also try using/forking |
Looking at the filtering / grouping requirements, we should be able to get away with a The |
@mathemancer makes sense. I do want to make it easy to extend to other URI parts in the future e.g. |
I do think it makes sense to try to use that extension (and other URI-mangling libraries) as inspiration at least. I just wish there was a good way to install extensions without access to the underlying server. |
This issue is to set up a data type to work with URIs. We might choose to use an existing extension like https://github.com/petere/pguri or write our own
MATHESAR_TYPES.URI
type. Part of this issue involves evaluating both options.As part of this issue, we need to do the following:
pguri
or write our own. @kgodey and @mathemancer should sign off before implementation.MATHESAR_TYPES.URI
custom type.Additional Context
v0/databases/
's types list to show both Mathesar and DB type information. #368 for code that calculates which types are allowed for a column.The text was updated successfully, but these errors were encountered: