Re: Warning: Current core (or exorcist perhaps) produces duplicate repligard table entries

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

- --Piotras wrote on 2006-03-02 14:41:
>>>> while newer versions prevent object creation in such a case (detected
>>>> by an UNIQUE INDEX, this is almost as bad as it prevents object
>>>> creation for obscure reasons to users).
>>> 
>>> Can you copy here some url which points to documentaion which says that
>>> object and it's record is not created in such case?
>> 
>> You have been advertising just this as a solution in IRC.
> 
> Yes, I said about repligard's record not being created. Because it doesn't
> matter what guid should be assigned for object in such case. If some guids
> for realm , id pair already exists then its automagically assigned itself to
> newly created object's record. Thus , no action is required here as long as
> MySQL prevents from duplicated records being created.

Great. You're reusing GUIDs possibly already in use in other places. Welcome
Data Chaos. Go on, continue like this, and you'll have me switch to another CMS
in not time.


Live long and Prosper!
Torben Nehmer

- --
Torben Nehmer, Guenzburg, Bavaria, Germany
http://www.nathan-syntronics.de, mailto:[email protected]
PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEBvr0JPh4Kn6d5FYRAr/tAKDjP70ORvLK1l2siNVzLWxb6kGJcACgqq51
aQGQSt2HiSbqlnL0NDZc56w=
=cAcd
-----END PGP SIGNATURE-----