Re: [Zope-dev] [BlueBream] disabling zope.schema constraint check in edit form

2011-08-19 Thread Joshua Immanuel
Hello Michael, On Thu, 2011-08-18 at 12:46 +0200, Michael Howitz wrote: Some time a ago I wrote a blog post about objects with attributes which are unique in their container [1]. Besides it is written in German you might get the clue from the code examples. [1]

Re: [Zope-dev] [BlueBream] disabling zope.schema constraint check in edit form

2011-08-18 Thread Michael Howitz
Am 18.08.2011 um 09:59 schrieb Joshua Immanuel: Hello all, I use the zope.schema field's constraint parameter to check for the uniqueness of a particular field like this class IMyObject(Interface): def check_for_uniqueness(value): cat =

Re: [Zope-dev] [BlueBream] disabling zope.schema constraint check in edit form

2011-08-18 Thread Joshua Immanuel
Hello Michael, Thanks for the reply. On Thu, 2011-08-18 at 12:46 +0200, Michael Howitz wrote: Is there a way to disable the constraint check in the EditForm if the 'name' field isn't modified? Make sure your catalog search does not return the object you are currently editing. Yes. But

Re: [Zope-dev] [BlueBream] disabling zope.schema constraint check in edit form

2011-08-18 Thread Charlie Clark
Am 18.08.2011, 13:19 Uhr, schrieb Joshua Immanuel j...@hipro.co.in: Yes. But considering the fact that I am doing this check at the interface level. I wonder if that is ever possible, because the constraint method knows just the value of the field. You can always go from the field to the