Hi all,
I have tried to understand repligard's (and the staging-to-live
mechanism's) internals. Now, a minor question:
In the downgrade_unapproved.pl, there is a comment:
#BUILD THE IN BIT FOR
#update repligard set updated=NULL where id in (1,2,3,4);
# this will make the updated > than changed and hence ignore it.
#
#ALSO BUILD
#update repligard set updated=0 where id in (5,6,7) for the force bit.
I do not understand. I you set updated=NULL then updated>changed will
return NULL (which means false, AFAIK). And here is the mysql.log from a
repligard import run:
SELECT id FROM repligard WHERE guid='5317402febf4493f8c75e45550c5b440'
SELECT id FROM topic WHERE (id=14) AND (sitegroup IN (0,0) OR 1<>0)
SELECT id,guid,realm,changed,updated,action FROM repligard WHERE
guid='5317402febf4493f8c75e45550c5b440'
UPDATE topic SET code='', up='0', score='0', description='', extra='',
creator='8', revised='2002-01-18 16:15:14', revision='0', revisor='8',
name='informed'
, created='2002-01-18 16:15:14', sitegroup='1', owner='5' WHERE id=14
AND (sitegroup = 0 OR 1<>0)
UPDATE repligard SET changed='20020122192317',action='update' WHERE
id=14 AND realm='topic'
UPDATE repligard SET updated=NULL WHERE id=14 AND realm='topic'
SELECT changed FROM repligard WHERE
guid='5317402febf4493f8c75e45550c5b440'
SELECT updated FROM repligard WHERE
guid='5317402febf4493f8c75e45550c5b440'
SELECT id FROM repligard WHERE guid='5317402febf4493f8c75e45550c5b440'
I do not understand why updated isn't the actual date?
(Anyway, currently this whole staging-to-live is a big magic for me, but
in repligard_staging_to_live.sh, the following cmd is executed twice:
$REPLIGARD -c /etc/repligard/repligard_hourly_import_live.conf \
-i /tmp/hourly_export_${THISDATE}.xml.gz
Is it intentional?
Bye:
Circum
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
