Open andreaBelmont opened 4 years ago
Correct me if I'm wrong.
But shouldn't the Pengines side of things be responsible for consulting?
This is basically just an API for working with an already running Pengines service.
So by my reading -- you are correct -- it is "wasteful" to include the consult in the Python side of the service, though you have the right to do so.
However, most (sane, well scoped) use cases that would probably be a code smell.
Thinking a bit more, consulting is a happy path -- would you mind adding an example to the readme that handles this case once you are happy with your approach?
I am not quite sure how does this work:
Do I always need to load the database each time I run a query? Is there any better way to consult a database of prolog facts? I looked in the examples but I could not really find an example of
:- consult('file.pl')
Thanks for helping