On Sat, Dec 30, 2000 at 06:47:27PM +0800, Alan Knowles wrote:
>
> > > | mysql> describe repligard;
> > > | +-----------+-------------+------+-----+---------------------+-------+
> > > | | Field | Type | Null | Key | Default | Extra |
> > > | +-----------+-------------+------+-----+---------------------+-------+
> > > | | id | int(11) | | | 0 | |
> > > | | timestamp | datetime | | | 0000-00-00 00:00:00 | |
> > > | | updated | datetime | | | 0000-00-00 00:00:00 | |
> > > | | realm | varchar(32) | | | | |
> > > | | tag | varchar(32) | | MUL | | |
> > > | | sitegroup | int(11) | | | 0 | |
> > > | +-----------+-------------+------+-----+---------------------+-------+
> > > | 6 rows in set (0.00 sec)
> > Yes, this is correct.
Oh, I've looked in wrong place. Indeed, it is old code. New one is
CREATE TABLE repligard (
# Local ID of resource in its own table
id int(11) DEFAULT '0' NOT NULL,
# timestamp of last change of resource from application side
changed timestamp(14),
# timestamp of last change of resource from Repligard side
updated timestamp(14),
# Resource's table name.
realm varchar(32) DEFAULT '' NOT NULL,
# Globally Unique IDentifier
guid varchar(32) DEFAULT '' NOT NULL,
# Last action performed on resource
action enum('create','update','delete') DEFAULT 'create' NOT NULL,
# Sitegroup for resource
sitegroup int(11) DEFAULT '0' NOT NULL,
PRIMARY KEY (guid),
KEY realm (realm,id)
);
> Are you sure, I had a similar set of problems upgrading our main server, (not
> helped by problems with apache 1.3.14 (from debian-woody) which appears to
> refuse to work with midgard due to some problems with the regcomp library.. -
> ended up down grading to 1.3.9 (from potato).)
>
> anyway my table looks like this (note the GUID is not in the table above ....)
>
> mysql> describe repligard;
>
>+-----------+----------------------------------+------+-----+---------------------+----------------+----------------------+
> | Field | Type | Null | Key |
> Default | Extra | Privileges |
>
>+-----------+----------------------------------+------+-----+---------------------+----------------+----------------------+
> | autoid | int(11) | | PRI |
> NULL | auto_increment | select,insert,update |
I never created this field and Repligard code never had links to it.
Why database-upgrade script had it inside?
> | id | int(11) | | |
> 0 | | select,insert,update |
> | timestamp | datetime | | | 0000-00-00
> 00:00:00 | | select,insert,update |
> | updated | datetime | | | 0000-00-00
> 00:00:00 | | select,insert,update |
> | realm | varchar(32) | |
> | | | select,insert,update |
> | tag | varchar(32) | | MUL
> | | | select,insert,update |
> | sitegroup | int(11) | | |
> 0 | | select,insert,update |
> | guid | varchar(32) | YES | |
> NULL | | select,insert,update |
> | action | enum('create','update','delete') | YES | |
> create | | select,insert,update |
> | changed | timestamp(14) | YES | |
> NULL | | select,insert,update |
>
>+-----------+----------------------------------+------+-----+---------------------+----------------+----------------------+
> 10 rows in set (0.00 sec)
I see, your table is wrong. Emile has put wrong repligard table into
database-upgrade sometime ago and hasn't updated script when format was
changed (my fault too). Also, it seems that your table is result of
ALTERing table structure, not recreating from the beginning. I've fixed
it in CVS right after release (and correct data package is on the site).
Database-upgrade script became a source for numerous problems...
--
Sincerely yours, Alexander Bokovoy
The Midgard Project | www.midgard-project.org | Aurora R&D team
Minsk Linux Users Group | www.minsk-lug.net | www.aurora-linux.com
IPLabs Linux Team | linux.iplabs.ru | Architecte Open Source
-- Never look a gift horse in the mouth.
-- Saint Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
