Instead of getting (deleted and untracked files): ``` $ git status # On branch master # Your branch is ahead of 'origin/master' by 20 commits. # # Changes not staged for commit: # (use "git add/rm <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # deleted: cdb_dataservices_server--0.20.0--0.21.0.sql # deleted: cdb_dataservices_server--0.21.0--0.20.0.sql # deleted: cdb_dataservices_server--0.21.0.sql # modified: cdb_dataservices_server.control # # Untracked files: # (use "git add <file>..." to include in what will be committed) # # cdb_dataservices_server--0.21.0--0.22.0.sql # cdb_dataservices_server--0.22.0--0.21.0.sql # cdb_dataservices_server--0.22.0.sql # old_versions/cdb_dataservices_server--0.20.0--0.21.0.sql # old_versions/cdb_dataservices_server--0.21.0--0.20.0.sql # old_versions/cdb_dataservices_server--0.21.0.sql no changes added to commit (use "git add" and/or "git commit -a") ``` you'd get something like: ``` $ git status # On branch master # Your branch is ahead of 'origin/master' by 20 commits. # # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # renamed: cdb_dataservices_server--0.20.0--0.21.0.sql -> old_versions/cdb_dataservices_server--0.20.0--0.21.0.sql # renamed: cdb_dataservices_server--0.21.0--0.20.0.sql -> old_versions/cdb_dataservices_server--0.21.0--0.20.0.sql # renamed: cdb_dataservices_server--0.21.0.sql -> old_versions/cdb_dataservices_server--0.21.0.sql # # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: cdb_dataservices_server.control # # Untracked files: # (use "git add <file>..." to include in what will be committed) # # cdb_dataservices_server--0.21.0--0.22.0.sql # cdb_dataservices_server--0.22.0--0.21.0.sql # cdb_dataservices_server--0.22.0.sql ``` which is nicer IMHO.
CARTO Data Services API server extension
Postgres extension for the CARTO Data Services API, server side.
Dependencies
This extension is thought to be used on top of CARTO geocoder extension, for the internal geocoder.
The following is a non-comprehensive list of dependencies:
- Postgres 9.3+
- Postgis extension
- Schema triggers extension
- cartodb-postgresql CARTO extension
Installation into the db cluster
This requires root privileges
sudo make all install
Execute tests
PGUSER=postgres make installcheck
Build, install & test
One-liner:
sudo PGUSER=postgres make all install installcheck
Install onto a CARTO user's database
Remember that is mandatory to install it on top of cdb_geocoder
psql -U postgres cartodb_dev_user_fe3b850a-01c0-48f9-8a26-a82f09e9b53f_db
and then:
CREATE EXTENSION cdb_dataservices_server;
The extension creation in the user's db requires superuser privileges.