On Apr 13, 6:49 am, Felix Schwarz <[EMAIL PROTECTED]> wrote:
...
> I'm not entirely sure if I understood your problem 100% but it looks like
> you are annoyed by the same bug/feature/behavior which took me several
> hours to track down.

Indeed it does look like the same bug, particularly the failure to
call validate twice during the same request.

> I wrote some documentation back then, maybe you can look at this 
> paragraph:http://docs.turbogears.org/1.0/ValidateDecorator#beware-of-the-recurs...
>
> Honestly, I'm not sure why the recursion guard was put in in the first
> place. I only did some quick experiments when I removed the check and
> everything seemed to work but removing this in 1.0 will almost certainly
> break some applications.

Sigh.  I guess we may wind up having to use a fixed version of
@validate for our application then, just something that does a
straightforward validate whenever the function is called, regardless
of what else has happened... or something.

The real thrust of my question was more "what am I doing that's not
'normal' here"?

It seems to me like this is the *normal* use case for validators, how
can it be broken and yet people use the TurboGears system?  I ran into
this on day one, with an extremely simple CRUD-style application, how
could the whole TurboGears community not run into it daily unless they
are doing something fundamentally different?

* Are people really not using validation rigorously enough to run into
it (save for yourself)?

* Are they using a traversal pattern for the "subject lookup" stuff
and thus never using the validators for object lookup/resolution?

I'm reasonably early in this project, so if there is an anti-pattern
I'm coding into the application here I'd like to avoid it rather than
hack around the system's services to support my anti-pattern.

Thanks,
Mike
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to