YAGo has problems with MySQL

I decided to work with YAGO (A huge semantic knowledge base) on my MySQL DBMS. So, I used it’s javatools to import it to my MySQL and today (Nov. 18th, 2009), after 6 days that MySQL was indexing the data, when we contacted the authors, they told us that YAGO has problems with MySQL, because of indexing values longer than 256. So, they suggested that we use PostGre.

Here is the log of my 6 days:

Creating indices on facts…
  The following indexes will be created:
CREATE INDEX factsidIndex ON facts (id)
CREATE INDEX factsarg1Index ON facts (arg1)
CREATE INDEX factsarg2Index ON facts (arg2)
CREATE INDEX factsrelationIndex ON facts (relation)
CREATE INDEX factsrelationarg1Index ON facts (relation, arg1)
CREATE INDEX factsrelationarg2Index ON facts (relation, arg2)
CREATE INDEX factsarg1arg2Index ON facts (arg1, arg2)
  On some systems, this fails. In these cases, please interrupt and create the indexes manually.
CREATE INDEX factsidIndex ON facts (id)… done (42 min, 30 s)
CREATE INDEX factsarg1Index ON facts (arg1)… done (9 h, 16 min)
CREATE INDEX factsarg2Index ON facts (arg2)… done (18 h, 5 min)
CREATE INDEX factsrelationIndex ON facts (relation)… done (19 h, 20 min)
CREATE INDEX factsrelationarg1Index ON facts (relation, arg1)… done (40 h, 19 min)
CREATE INDEX factsrelationarg2Index ON facts (relation, arg2)… done (57 h, 22 min)
CREATE INDEX factsarg1arg2Index ON facts (arg1, arg2)…

—

Reza++