The obvious answer (obvious to me at least) is to use Erlog or a development of it.<br><br>- You can do nice querying into a database. I did a simple Ets interface to Erlog which takes a pattern (prolog term) and returns successive matches to it over backtracking binding unbound variables.
<br><br>- It is integrated into Erlang concerning data.<br><br>- You don't define Erlog procedures as Erlang code, but this could be done using parse transforms. Someone "just" has to do an interface to the "right" database.
<br><br>- It would be difficult to just directly call an Erlog procedure, even if it was written in Erlang, as you need a context for it to work in which is not the same as for normal Erlang code.<br><br>I never went further with Erlog as no-one came back with request/suggestions for how it could be developed. But I am open to suggestion
<br><br><div><span class="gmail_quote">On 30/11/2007, <b class="gmail_sendername">Joe Armstrong</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Question:<br><br>A long time ago Erlang started as a extension to Prolog ...<br><br>Now Prolog is a wonderful language for querying databases in -<br><<forget this SQL stuff it's horrendously verbose compared to Prolog queries>>
<br><br>So why when we talk about Erlang + an external data base do we<br>automatically reach for an SQL data base?<br><br>I haven't been actively following the Prolog world, so here's my questions:<br><br>Are there any prolog data bases with ACID properties.
<br><br>I'd like something that is<br><br> - open source<br> - resident (is runs like mySQL as a resident task on my machine)<br> - can handle large amounts of data (meaning I could store several<br>giga facts in the DB)
<br> - has ACID properties<br><br>Given the similarity between Erlang and Prolog data structures<br>integration between the two languages<br>could be very nice.<br><br>Embedded prolog queries in Erlang would be *very* nice, just
<br>interpreting erlang variables<br>as prolog logical variables.<br><br>Comments anybody?<br><br>/Joe Armstrong<br>_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:email@example.com">