Pierre van Rooden <[EMAIL PROTECTED]> wrote: > > - mm:createnode makeuniques='true' > > The 'unique' fields are automaticly filled with a unique value to > > start with > > Seems pretty ugly to me, especially since I can't think of a way to > generate a sensible unique value .
It depends a bit. E.g. for an integer field it's doing the smallest positive integer available, which does make sense. > Why not use a builder class to fill a unique field with data? Yes, perhaps it was a mistake to add it. But still. - now you can choose to use it or not - uniqueness is defined in the builder xml (I think with 'key'..sigh) so independently of the implementation - generating the uniqueness in getNewNode of MMObjectBuilder must be even simpler, because you have no cloud- or page-environment there (e.g. no Locale, no User object, no request object). Perhaps i made it a bit to quickly why creating the security editors. It allowed me to rapidly create a user without thinking up a new username each time (Gebruiker1, Gebruiker2...) But I think I agree that I'd perhaps better remove it again :-) Michiel -- Michiel Meeuwissen Mediapark C101 Hilversum +31 (0)35 6772979 nl_NL eo_XX en_US mihxil' [] ()
