At 15:35 Uhr +0200 18.08.2003, Alexander Rigo wrote: Hi,
i want to discuss the way i've solved my problem with two different databases in nadmin studio. The problem was that deleted articles and pages are not replicated correctly. So the solution for me is:
## # to prepare everything in the staging-db to export mysql midgardstaging -e "update repligard set changed=NULL"
# export everything from the staging-db repligard -c repligard_hourly_dump.conf -e mydump.xmlgz
# clear some relevant tables mysql midgardlive -e "delete * from article" mysql midgardlive -e "delete * from element" mysql midgardlive -e "delete * from page" mysql midgardlive -e "delete * from record_extension" mysql midgardlive -e "delete * from topic" mysql midgardlive -e "delete * from blobs"
# import from the staging-DB repligard -c repligard_hourly_import_live.conf -i mydump.xmlgz ##
As far as i can say it works. But i'm not deep enough into the database structure of nadmin/midgard to say that the way i described is entirely right.Maybe some as a comment or a better way?
Regards, Alex
Hello Alex,
I'm no midgard developer but as far as I see You action does not have any affect to the midgard data. The repligard table not only contains the time of the last action that has been taken to an entity but also information about what action has taken to it (action field can contain 'create', 'update', 'delete'). In your case this field seems to contain errors but you does not fix them by your trial to repair the database.
Unfortunately, I don't know neither a tool which is able to validate the consistency of the midgard database data nor to rebuild the repligard table from the rest of the midgard db. Repligard doesn't do so, does it?
I would think the only way is to repair the database by hand ...
Regards, Axel
-- [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
