-
Notifications
You must be signed in to change notification settings - Fork 24
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
Merge TiFeatures and TiMVT #1
Comments
Function introspection in this branch is working and looks for any function that matches this signature:
In an empty PostgreSQL database with PostGIS installed, with no settings to change what schemas/tables/functions are whitelisted, the following native PostGIS functions will be made available:
Note that with this set up, the functions are expected to return geometry and when vector tiles are requested, TiPG will automatically wrap the function with calls to ST_ASMVT/ST_ASMVTGEOM. |
@bitner I think the last missing piece is custom function support. TODO
|
I don't actually like the file based function support. The "idea" of this library (at least to me) is that it never writes/changes anything in the database and that you should manage tables/functions directly in the database. My opinion (not strongly held, so definitely willing to consider the file based functions) is that TiPG should be able to fully run as a Read Only user (this would change if we add transaction support to tables). Ideally, for security, the user that TiPG connects as should not have the ability (even if we add transaction support) to create/drop any new tables/views/functions. I know that this will hardly ever be the case and most people will just be deploying using an admin user, but I'd still like to see us encouraging that best practice and the file based functions runs counter to that. |
Initial checklist for Merging TiFeatures and TiMVT into TiPG
TiPG is intended to merge the features of TiFeatures and TiMVT into a project in order to reduce duplication between the two projects.
The text was updated successfully, but these errors were encountered: