Hello, > On a recieving database to force update > > mysql midgardstaging -e "update repligard set updated=0,changed=0" > > then run the repligard import command > > - it may help to repeat this step twice! [...] > On a sending database to force it to update a recieving database > > mysql midgardstaging -e "update repligard set changed=NULL" > > then run the repligard export command.
It helped, and I really have to repeat it thrice, as at the first run all the data belonged to my new sitegroup was attached to SG0! At the 2nd try, it hopefully corrected this mistake, but a few page was still in SG0. This repligard is not the state-of-the-art technology yet... :( Anyway, is nadmin development dead? Who developes/maintains it? The hklc site is not update since at least a year. On the http://cms.polarmedia.no/midgard there is a TNG dir which is older that 2001... Is it a new snapshot of nadmin, or what? Thanks for the help, bye: Circum PS: BTW, if I just copy my staging db to the place of the live database, does it have any drawbacks in contrast of replicating it with the method described above? It would be _much_ quicker and memory conservative (the repligard process takes about 245MB of ram, and last at least 15-20 minutes...) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
