Re: Protege db schema conversion
Todd Detwiler <[email protected]>
| Newsgroups | gmane.comp.misc.ontology.protege.general |
|---|---|
| Message-ID | <[email protected]> |
Hmmm, I wonder why it works for you but not me. I noticed the problem right after converting to a database. And, I tried it with several versions of Protege. All produced bad databases (presumably all like the one I sent you). Could it have something to do with mysql, like what engine I am using (i.e. myisam vs. innodb), or the db version, or the encoding? I see that, in a subsequent message, you sent me a link to the db you produced. I will check it out, thank you. Ultimately I will need to do this again. So, if you have any further insight, it would be helpful. Landon Todd Detwiler Structural Informatics Group (SIG) University of Washington phone: 206-616-2336 On 12/10/12 8:37 AM, [email protected] wrote: > Message: 2 > Date: Mon, 10 Dec 2012 08:31:51 -0800 > From: Timothy Redmond<[email protected]> > To:[email protected] > Subject: Re: [protege-discussion] Protege db schema conversion > Message-ID:<[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > I don't know if this is good news or bad news but when I converted the > clips file to the database format I had no problems. I made a mysql > dump, reloaded it and that was fine also. Later - when I have a faster > connection - I will give a link to the sql dump file. > > Did you notice the problem right after doing the conversion to database > format or did it only occur after making a sql dump and reloading it? I > am trying to figure out what is different about how I did things and how > you did things. > > -Timothy _______________________________________________ protege-discussion mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/protege-discussion Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03