> Wait, this means that sitegroup with the same GUID already existed? > If so then I don't understand your problem.
The existing sitegroup has been 'worked around' by eleminating the sitegroup field inside of the xml file ? (sorry for that, but I still have questions) > What do you understand by 'conflicting'? Repligard definition of conflict > is 'has same GUID'. I understood that every record in a sitegroup has a sitegroup id. If there already exist a sitegroup with a given id then the sitegroup to be importet may conflict with it > > What if the SG to be importet already exists on the new midgard ? > Then 'changed' field comes to game. Repligard does not treat sitegroups > specifically but libmidgard does. So what is after the import ? Changes libmidgard every sitegroup id during the import ? Let's avoid misunderstandings: We are talking about the id field now not the GUIDs. Usual records have autoincrement to avoid conflicting record ids. The sitegroup id is also a unique id. I'd like to know if there is also a dynamic mechanism like autoincrement to ensure uniqueness ? If so, how is sitegroup id managed ? If not, why is uniqueness of sitegroup's id not required ? dieter -- Kind regards Dieter Heine Systemadministration Unix Astrium GmbH Raumfahrt Bremen EMail: [EMAIL PROTECTED] Fax: 49 421 539 5698 Phone: 49 421 539 4989 User Help Desk Astrium Hamburg Phone (office Bremen): on request --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
