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

Meeting 31 May: About flow of control in pgRouting #20

Open
thisisashukla opened this issue Jun 2, 2017 · 1 comment
Open

Meeting 31 May: About flow of control in pgRouting #20

thisisashukla opened this issue Jun 2, 2017 · 1 comment
Labels

Comments

@thisisashukla
Copy link
Owner

SQL -> fn C code -> process -> _driver.h is C/C++ -> _driver.cpp -> C++(does it all)

@thisisashukla
Copy link
Owner Author

The Flow of Control for a pgRouting function is as follows:

1. SQL File: sql\myFunction\myFunction.sql -> This file contains the signature of the function and calls the C function code of the function

2. C Code: src\myFunction\src\myFunction.c -> This file contains myFunction's call to process. The C code retrieves the arguments from the PostgreSQL parameters and converts them to corresponding C types.

3. C/C++ Driver: include\drivers\myFunction\myFunction_driver.h -> This file contains both C and C++ code and this links the C function to the C++ driver

4. C++ Driver: src\myFunction\src\myFunction_driver.cpp -> Connects the previous code to the C++ code

5. C++ Code: Contains the algorithm which performs the required tasks

6. Tests:

  • src\myFunction\test\test.conf-> Contains files for pgTap tests
  • src\myFunction\test\doc-myFunction.result & src\myFunction\test\doc-myFunction.sql -> Documentation tests files
  • src\myFunction\test\test.conf -> Configuration file for tests

@thisisashukla thisisashukla modified the milestone: First Jun 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant