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 = getUtility(ICatalog)
result
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):
>ca
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.
Am 18.08.2011, 13:19 Uhr, schrieb Joshua Immanuel :
> 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 object to which it
Hi Joshua,
On Thu, Aug 18, 2011 at 09:59, Joshua Immanuel wrote:
> [...] Worse case scenario is where I have a cancel
> action button which just redirects to another page, that too screams for
> the NameAlreadyExists error.
For the 'cancel button' case, you need to have a form action with a
vali
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/17/2011 12:01 PM, Gediminas Paulauskas wrote:
> 2011/8/6 Tres Seaver :
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 08/04/2011 10:18 AM, Gediminas Paulauskas wrote:
>>> Log message for revision 122462: Fix a regression introduced in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/17/2011 10:03 AM, Tres Seaver wrote:
>> [1]
>> http://buildbot.afpy.org/ztk1.0/builders/Python2.6.5%20Linux%2064bit/builds/344/steps/test%20ztk/logs/stdio
>
>>
> I
>
> cannot reproduce that failure. The assertion is actually
> backported, al
Hello Leonardo,
On Thu, 2011-08-18 at 19:10 +0200, Leonardo Rochael Almeida wrote:
> For the 'cancel button' case, you need to have a form action with a
> validator that always validates, no matter what. You can find an
> example of one such null_validator here:
>
> https://svn.plone.org/svn/plon
This is the summary for test reports received on the
zope-tests list between 2011-08-17 00:00:00 UTC and 2011-08-18 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/
