Opened 14 years ago

Closed 11 years ago

#14241 closed New feature (wontfix)

instructions for creating spatial database template differ on fedora 13 (64 bit)

Reported by: josdekloe Owned by: nobody
Component: Documentation Version: 1.2
Severity: Normal Keywords: fedora
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Creating a Spatial Database Template for PostGIS on a 64-bit Fedora 13 machine is slightly different from what is explained on
http://docs.djangoproject.com/en/dev/ref/contrib/gis/install/#spatialdb-template

This list of commands eventually did the trick for me:
(note the different POSTGIS_SQL_PATH pathname, and the addition of '-64' to the postgis.sql filename)

setenv POSTGIS_SQL_PATH /usr/share/pgsql/contrib
# Creating the template spatial database.[BR]]
createdb -E UTF8 template_postgis
createlang -d template_postgis plpgsql # Adding PLPGSQL language support.
# Allows non-superusers the ability to create from this template
psql -d postgres -c "UPDATE pg_database SET datistemplate='true' WHERE datname='template_postgis';"
# Loading the PostGIS SQL routines
psql -d template_postgis -f $POSTGIS_SQL_PATH/postgis-64.sql
psql -d template_postgis -f $POSTGIS_SQL_PATH/spatial_ref_sys.sql
# Enabling users to alter spatial tables
psql -d template_postgis -c "GRANT ALL ON geometry_columns TO PUBLIC;"
psql -d template_postgis -c "GRANT ALL ON geography_columns TO PUBLIC;"
psql -d template_postgis -c "GRANT ALL ON spatial_ref_sys TO PUBLIC;"

Change History (5)

comment:1 by Gabriel Hurley, 13 years ago

Triage Stage: UnreviewedAccepted

It seems like the most useful thing here would be to distill out the core of what's *different* about the process for Fedora 13 64-bit and explain that rather than simply pasting a separate script.

comment:2 by Graham King, 13 years ago

Keywords: fedora added
Severity: Normal
Type: New feature

comment:3 by Aymeric Augustin, 12 years ago

UI/UX: unset

Change UI/UX from NULL to False.

comment:4 by Aymeric Augustin, 12 years ago

Easy pickings: unset

Change Easy pickings from NULL to False.

comment:5 by Claude Paroz, 11 years ago

Resolution: wontfix
Status: newclosed

There is a note just above the command list: "The example below assumes PostGIS 1.5, thus you may need to modify POSTGIS_SQL_PATH and the name of the SQL file for the specific version of PostGIS you are using."

I don't think it would be possible to indicate variants for each distribution.

Note: See TracTickets for help on using tickets.
Back to Top