[postgis-devel] TIGER Geocoder setup

Paragon Corporation lr at pcorp.us
Sun May 29 17:17:12 PDT 2011


I didn't because a lot of people install into existing spatial databases
where they already have the search paths set so if I were to do that in the
script, I could break their other applications.

For example I have one client who has 5 items in his search schema mostly
for logical partitioning of which department is responsible for the data but
from an application standpoint is not relevant and some people like us like
to put their custom functions and data in separate schema from public but
don't want to schema qualify everytime they need to use them.

Though now that you mention it, I could put in that line remarked out so
people can manually edit and enable it  if they wanted to itemize the
schemas there.


-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of
maplabs at light42.com
Sent: Sunday, May 29, 2011 3:55 PM
To: postgis-devel at postgis.refractions.net
Subject: [postgis-devel] TIGER Geocoder setup

Why not just add the line

${PSQL_CMD} -d "${THEDB}" -c "ALTER DATABASE geocoder SET
search_path=public, tiger;"

  to create_geocode.sh, right after creating the tiger schema?


postgis-devel mailing list
postgis-devel at postgis.refractions.net

More information about the postgis-devel mailing list