German Poo Caaman~o wrote:
> En jue, 2001-11-08 a 19:27, Emiliano escribio:
> > German Poo C. wrote:
> > > Also, something were wrong with database-upgrade:
> > > DBD::mysql::st execute failed: Unknown column 'history.id' in 'field
> > > list' at ./database-upgrade line 418.
> > > !! Failed execute for 'history'
What does 'describe history' return when entered in the mysql command
line client?
> Me neither.
>
> Just:
> 418: if (!$sth->execute()) {
> 419: print " !! Failed execute for '$table'\n";
> 420: next;
> 421: }
The table name here is generated by mysql itself (I'm asking it to
return all table names), hence the test above. I've added code to
database-upgrade to skip over a table like this, so you can give it a
go; the updated version can be found in CVS, and for single files you
could easily picj it up from http://cvs.midgard-project.org/
> | history |
Odd... this is not part of midgard.
> > $ database-upgrade
> > $ repligard -m
> > $ database-upgrade # not necesary but will test if your database is OK
Try this procedure again with the updated database-upgrade.
> ++ Testing 'snippet'...
> ++ Testing 'snippetdir'...
> ++ Testing 'style'...
> ++ Testing 'topic'...
> There are 517 GUIDS missing! You will need to run 'repligard -m'.
BTW Alexander, the above run shows that the database upgrade
succeeded; it's ignoring the problem with the history table. So I
guess that still leaves a repligard problem.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
