From: Jonathan C. <cra...@sn...> - 2003-02-25 13:49:41
|
Paul- On Fri, 21 Feb 2003, pjm wrote: > I tried your instructions and did a: `ga +meta --commit` > Arnaud has setup the DB so maybe he knows why - I needed to create a record in > the MACHINE table so I created the following SQL; > > INSERT INTO MACHINE > (MACHINE_ID, > NAME, > CPUS, > MEMORY, > MODIFICATION_DATE, > USER_READ, > USER_WRITE, > GROUP_READ, > GROUP_WRITE, > OTHER_READ, > OTHER_WRITE, > ROW_USER_ID, > ROW_GROUP_ID, > ROW_PROJECT_ID, > ROW_ALG_INVOCATION_ID) > VALUES (0, 'Fake_machine', 1, 1, SYSDATE, 1,1,1,1,1,1,1,1,1,1); > > If this is useful I can create a new file called; > GUS/Model/schema/oracle/core-machine-row.sql > or something. If I shouldn't, please let me know :) > Anyway, creating this record made the `ga +meta --commit` work. I think we should just make the machine_id column nullable in core.AlgorithmInvocation; I noticed this problem with the reference to core.Machine a few weeks ago and I thought I'd changed the schema before putting it in CVS, but apparently not. This will go into the next release, and I'll start putting together the migration script today, since quite a few schema changes have been made since the initial 3.0 release. Jonathan |