Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding support for schemas and multiple tables, Attempt to fix issue 178 #185

Merged
merged 15 commits into from
Sep 5, 2013
Merged

Conversation

cvvergara
Copy link
Member

Support for schemas and multiple tables:
Modifications to: pgr_analyzeGraph (non sql version) pgr_analizeOneway pgr_createTopology
pgr_pointToId pgr_isColumnInTable pgr_isColumnIndexed
New fucntions: pgr_createVerticesTable
pgr_getTableName pgr_getColumnName

In some functions parameters were added to handle different names for "source" and "target"
Example: The vertices table created for table myschema,myedgetable is
myschema.myedgetable_vertices_pgr

@woodbri
Copy link
Contributor

woodbri commented Aug 23, 2013

looking this over, it seems that src/common/test/common-any-05.test is not correct because it ends in select * from vertices_tmp order by id; and this table does not exist. What should this table be named with the new code?

@woodbri woodbri merged commit 524c749 into pgRouting:develop Sep 5, 2013
@dkastl dkastl added this to the Release 2.0.0 milestone Mar 23, 2015
@dkastl dkastl removed the 2.0 label Mar 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants