Would it be a good idea to separate the Drupal admin user and Postgis user? They are not necessary the same
So add Postgis user credentials in settings

Comments

friedjoff’s picture

I guess you talk about database users. By default the Field API uses the main Drupal database configuration, so right now we have no possibility to specify a different database user. It should be possible to change this, but I'm not sure if it's worth the effort.

Can you provide some more details about your setup and the benefits of two different users?

avdp’s picture

Thanks, I guess I do not understand the general concept yet. Right now I can't test things because somehow the postgis installation went bad, gdal doesn't want to install anymore :(

I was under the impression that there is one postgres/postgis database with the gis-data and one regular drupal database? Is this correct? Or is this Drupal installed in the postgres database?

I have an aegir multisite setup, and would like to connect it to an existing postgis database (in this case on the same server). This database is the primary source. I was looking at geofield and the sync_postgis module, but in that case the drupal database is the primary.. I'm still in the learning phase, so if this sounds messy then that's why :)

So perhaps more in general the question would be what the best way is to communicate with an external postgis database, but it looks like you are already discussing this with the geofield guys.

Regards!

friedjoff’s picture

Title: PostGIS User » Support separate PostGIS database

Right now this module will store geospatial data in the regular Drupal database, so you need to intall Drupal in a PostgreSQL database with PostGIS enabled.

In the future we should support the configuration of a separate PostGIS database. See http://drupal.org/node/18429 on howto use different databases.

friedjoff’s picture

The Field API in Drupal 7 doesn't really seem to support field type specific storage backends, if the field gets created through the Field UI. Only the default field storage can be changed to a custom implementation.

The 7.x-1.x-storage branch provides an initial implementation of a custom field storage backend, but there is still a lot of work to do.

friedjoff’s picture

Status: Active » Postponed

This module won't support a separate PostGIS database for now. Try the Geofield and and Sync PostGIS modules if you really have to use a separate PostGIS database.

ulim’s picture

avdp:

The PostGIS module is part of Cartaro.org. There it is our core concept to bring together geospatial data with all other content of the CMS. It would be counterproductive to have things in two separate databases. You would e.g. be very restricted doing complex spatial SQL queries on both geometries and content. So for most setups we recommend having one single database.

Concerning Ægir: we have already explained in another thread, that Ægir is not ideal for our setup since it does neither support PostGIS nor other components of Cartaro like Geoserver.