<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>mark_l_watson</author><text>As a proof of concept, this looks very cool. Suggestion: add a short example to the README.&lt;p&gt;I had one experience with Prolog in the 1980s that blew my mind. I had an IR&amp;amp;D project to build a complete prototype of an air&amp;#x2F;land battle simulator (yes, I was a defense contractor back then) in Common Lisp given 6 weeks of coverage to write it and demo it. After a month I was satisfied with the functionality and after demoing it I asked permission to rewrite it in ExperProlog on the Mac (I had done the Common Lisp version in my Xerox 1108 Lisp Machine). In ten days time it was done, and also had nice graphics and UI extensions that the Common Lisp version did not have. Anyway, except for few small open source things, that was the only large project I ever did in Prolog.</text><parent_chain></parent_chain></comment><story><title>Prolog language for PostgreSQL proof of concept</title><url>https://github.com/tatut/pgprolog</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>larodi</author><text>Love this, I&amp;#x27;ve long considered that this should&amp;#x27;ve been made as Prolog and SQL are ternary logic and basically SQL derives from Datalog and it itself from Prolog. A table record can be taught as of as a Prolog fact, so this makes the WHERE clauses the predicates in the conjunction on the right-hand side of a rule. And then exhausting the goal is actually returning the result-set.&lt;p&gt;Hope to see this develop even further, as Prolog has its place with relational databases.</text><parent_chain></parent_chain></comment><story><title>Prolog language for PostgreSQL proof of concept</title><url>https://github.com/tatut/pgprolog</url></story>