[pgrouting-users] Table location

[Stephen Woodbridge]

I cloned vertex assignment code to change it for zlevels and it was 
trivial to make it run in another schema. I think all you need to do is:

1. remove all the explicit references to "public." from the stored 
procedure and reload it in you "data." schema

2. then make sure you set the default db search path like:

alter database mydb set search_path to data, public;

And everything is good.

-Steve

On 1/28/2011 1:39 AM, Dan Putler wrote:
> Given your comment on vertex assignments needing to be done in the
> public schema, I'm now not sure. I may have had a problem with the
> vertex assignments, looked through that code and discovered that it
> didn't handle anything other than the public schema well, and just put
> everything in public after that. I did this in July, so things are on
> the hazy side. What I was working on isn't part of a web application,
> and I am behind a firewall, so I was safe in keeping everything in the
> public schema.
>
> Dan
>
>
> --- On *Thu, 1/27/11, Henrik Berggren /<henke.berggren at gmail.com>/* wrote:
>
>
>     From: Henrik Berggren <henke.berggren at gmail.com>
>     Subject: Re: [pgrouting-users] Table location
>     To: "pgRouting users mailing list" <pgrouting-users at lists.osgeo.org>
>     Received: Thursday, January 27, 2011, 10:26 AM
>
>     Are you sure about that the data needs to be in the public schema
>     for shooting_star to work properly?
>
>     /Henrik
>
>     On 01/27/2011 07:06 PM, Dan Putler wrote:
>>     I also found that I could only use pgrouting with a data table
>>     that are in the public schema. My memory is that in some of the
>>     functions (I know this is true for the shooting star algorithm),
>>     the public schema is "hard wired" within the code.
>>
>>     Dan
>>
>>     --- On *Thu, 1/27/11, Daniel Kastl /<daniel at georepublic.de>
>>     </mc/compose?to=daniel at georepublic.de>/* wrote:
>>
>>
>>         From: Daniel Kastl <daniel at georepublic.de>
>>         </mc/compose?to=daniel at georepublic.de>
>>         Subject: Re: [pgrouting-users] Table location
>>         To: "pgRouting users mailing list"
>>         <pgrouting-users at lists.osgeo.org>
>>         </mc/compose?to=pgrouting-users at lists.osgeo.org>
>>         Received: Thursday, January 27, 2011, 8:18 AM
>>
>>         Good question, Ricardo!
>>         And thank you for sharing your experience, Henrik.
>>
>>         I must admit I haven't tried it, and probably the majority of
>>         users always works in public schema.
>>         I added a ticket not to forget about this, because I think it
>>         would be nice to support the schema in all functions:
>>         https://github.com/pgRouting/pgrouting/issues/issue/24
>>
>>         Daniel
>>
>>
>>         2011/1/28 Henrik Berggren <henke.berggren at gmail.com>
>>
>>             You can have it in other schemes but you need to run the
>>             assign_vertex_id in the public scheme, that is my experience.
>>
>>             /H
>>
>>
>>
>>             On 01/25/2011 10:42 PM, Ricardo Bayley wrote:
>>>             Hi everyone,
>>>
>>>             I am wondering, does pgrouting require to have tables on
>>>             the public schema ? or could they be on any schema ?
>>>
>>>
>>>             Thanks,
>>>
>>>
>>>             Ricardo
>>>
>>>             _______________________________________________
>>>             Pgrouting-users mailing list
>>>             Pgrouting-users at lists.osgeo.org
>>>             http://lists.osgeo.org/mailman/listinfo/pgrouting-users
>>
>>             _______________________________________________
>>             Pgrouting-users mailing list
>>             Pgrouting-users at lists.osgeo.org
>>             http://lists.osgeo.org/mailman/listinfo/pgrouting-users
>>
>>
>>
>>
>>         --
>>         Georepublic UG & Georepublic Japan
>>         eMail: daniel.kastl at georepublic.de
>>         Web: http://georepublic.de <http://georepublic.de/>
>>
>>         -----Inline Attachment Follows-----
>>
>>         _______________________________________________
>>         Pgrouting-users mailing list
>>         Pgrouting-users at lists.osgeo.org
>>         http://lists.osgeo.org/mailman/listinfo/pgrouting-users
>>
>>
>>
>>     _______________________________________________
>>     Pgrouting-users mailing list
>>     Pgrouting-users at lists.osgeo.org  </mc/compose?to=Pgrouting-users at lists.osgeo.org>
>>     http://lists.osgeo.org/mailman/listinfo/pgrouting-users
>
>     -----Inline Attachment Follows-----
>
>     _______________________________________________
>     Pgrouting-users mailing list
>     Pgrouting-users at lists.osgeo.org
>     </mc/compose?to=Pgrouting-users at lists.osgeo.org>
>     http://lists.osgeo.org/mailman/listinfo/pgrouting-users
>
>
>
>
> _______________________________________________
> Pgrouting-users mailing list
> Pgrouting-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-users