Article View: comp.lang.prolog
Article #285Re: set predicates for db-access
From: Karen A. Morrissey
Date: Wed, 16 Aug 1989 20:00
Date: Wed, 16 Aug 1989 20:00
17 lines
906 bytes
906 bytes
About 3-4 years ago, we bolted together C-Prolog 1.5 and 2 different proprietary relational database managers. Programmers could define predicates that mapped to relations as if a relation was a collection of grounded unit clauses. We even handled transaction processing (commit and abort). The interface was transparent except for the unsurprising temporal problems with additions and deletions. In practice it worked just fine. Karen Morrissey AT&T Bell Labs 303-538-4587 att!druhi!kam
Technical Details
Message-ID:
<4513@druhi.ATT.COM>Path:
arc1-ca.pugleaf.net!utzoo!attcan!utgpu!watmath!att!mtuxo!mtgzz!drutx!druhi!kamReferences:
<303@unizh.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!utgpu!watmath!att!mtuxo!mtgzz!drutx!druhi!kam From: kam@druhi.ATT.COM (Karen A. Morrissey) Newsgroups: comp.lang.prolog Subject: Re: set predicates for db-access Summary: minimal mismatch Keywords: prolog, database, set predicates Message-ID: <4513@druhi.ATT.COM> Date: 16 Aug 89 20:00:45 GMT References: <303@unizh.UUCP> Organization: AT&T, Denver, CO Lines: 17