Adding support for schemas and multiple tables, Attempt to fix issue 178 #185
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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