large databases

Hello,

I am trying to work with large databases. Most Prologs seem to be
unable to load databases whose size surpasses a certain limit. An
example: I had both Swi and Yap load a 3.1G database. Swi ran several
days until I stopped the experiment. Yap produced a segmentation fault
after a few minutes.

Are there any tricks for loading such databases?

Note that splitting a database up is not always a solution. Sometimes
one wants to be able to easily compare all facts with all other facts.

Simon
.

Relevant Pages

  • Re: large databases
    ... I am trying to work with large databases. ... Most Prologs seem to be ... unable to load databases whose size surpasses a certain limit. ... I had both Swi and Yap load a 3.1G database. ...
    (comp.lang.prolog)
  • Re: Protective niche for Borrelia burgdorferi to evade humoral immunity.
    ... I pay attention to what you are saying, although it is not really wise to ... I merely mention the facts so that anyone who is not as lazy as you are, ... software company and have no time to keep databases. ...
    (sci.med.diseases.lyme)
  • Re: Copyrighted Game Records
    ... AFAIK there is not much protection for databases of non-copyrighted facts ...
    (rec.games.go)
  • mySQL v. postgreSQL
    ... Anyone have any definitive differences betweeen these two databases in terms ... of performance, scalability, ease of use, utilities, etc? ... facts and/or anecdotal truths - not opinions. ...
    (comp.databases)