[postgis-users] Postgis 2.0 wishlist

[Paul Ramsey]

Another thing that is easy to do in a packaged environment but hard  
to do in a source code environment...

The packaged windows install could install PostGIS in a schema inside  
template_postgis, and getting a schema-installed PostGIS would just  
involve copying template_postgis. It could also include that schema  
in the default search path automatically.

Same thing could happen in RPM or DEB distributions, though I am  
always sceptical of packaged versions of PgSQL (the requirement for  
dump/restore of database through releases means that upgrading can be  
tricky to say the least).

P

On 15-May-07, at 3:57 PM, Willy-Bas Loos wrote:

> fair enough, sounds like that should be no problem. I should also  
> look up how to make a system schema in postgresql so that postgis  
> system objects do not end up in my backups (or if this only a  
> feature of pg_dump?), then how to make the new postgis schema a  
> default search path in postgresql (so that i can still omit the  
> schema name or search_path when calling the function).
>
> Still it seems to me that some of the people that make add-ons  
> should talk to postgresql people to integrate their functions and  
> other objects in a more comfortable manner.
> Then again, maybe it´s just the way it is.
>
> WBL
>
> On 5/15/07, David William Bitner <david.bitner at gmail.com> wrote:  
> Install postgis into whatever schema you want and set the default  
> search path in your postgresql configuration to use your postgis  
> schema in the default search path.  PostGIS is an add-on to  
> PostgreSQL, as such there is no out-of-the-box schema other than  
> public for it to use.
>
>
> On 5/15/07, Willy-Bas Loos < willybas at gmail.com> wrote: >This is  
> doable now, the main problem for newbies seems to be setting
> >the search_path every single time so they have access to them.
> That doesn´t seem logical to me: it´s also a problem for the same  
> newbies to restore their PostGIS databases.
>
> It should be a default search_path, just like pg_catalog and public.
> I dont need to set the search_path to use "select int2('25'::text)"  
> either.
> Or would that conflict with PostgreSQL policies?
>
> WBL
>
>
>
> On 5/15/07, Paul Ramsey < pramsey at refractions.net> wrote:
> On 15-May-07, at 4:33 AM, Willy-Bas Loos wrote:
>
> > If you're changing alle the function names, maybe it's time to make
> > system objects of them, stored in a seperate system schema (along
> > with the types, operators, etc)?
>
> This is doable now, the main problem for newbies seems to be setting
> the search_path every single time so they have access to them.
>
> > Other than that it would be nice to add descriptions to the
> > functions and operators in SQL, e.g. to indicate what the input for
> > each function should be when the number of arguments varies for
> > functions with equal names.
>
> How does one recover those descriptions at the commandline? Does \d
> functionname work?
>
> P
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
>
>
> -- 
> ************************************
> David William Bitner
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users