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
pgRouting SQL coding standard for documents and examples #386
Comments
Probably not worth the effort. The reason PostGIS does that is to satisfy SQL/MM convention (and then we said might as well make all our functions that way even if they aren't SQL/MM to minimize on confusion). Since your functions aren't SQL/MM defined, you have no precedence for it. You just need to be consistent within your own functions/documentation which I think you are. |
Okay. Thanks for confirmation. I found some inconsistencies in |
I think that we roughly were mimicing the postgis style because we are dependent on postgis so again just trying to be consistent. I don't think we are rigid about this or have even documented that we have a style. We might want to add a style guide statement to the development standards docs. |
@woodbri Okay. Thanks for comment. |
Eventually we need a pgRouting standard on function names:
But I think also it will need a full review of how the family of functions are formed |
#400 is related |
PostGIS documents seem to be written by a certain rule (
ST_XyzAbc
and upper case SQL words .etc).Should we follow the SQL coding standard except pgRouting function name (
pgr_xyzAbc
.etc) ?The text was updated successfully, but these errors were encountered: