> yeah didn't want to step on your toes but I got very excited about trying
it out 😅
Don't worry about that, it's a good thing this motivated you enough to
advance on this topic.
> I have a slight preference for the second option as it seems like it
could be used in other context than constrai
> It looks like you went even further than that :D.
yeah didn't want to step on your toes but I got very excited about trying
it out 😅
> Should we still add Q.check() (which will be as you said before), then
refactor BaseConstraint.validate() to use it?
I think it would still be worth doing to
I in favor with René Fleschenberg's proposal to enforce localization using
a template filter.
It happened too often, that someone forgot to unlocalize a primary key in
their templates
causing unwanted results.
--
You received this message because you are subscribed to the Google Groups
"Django
Hi Claude,
> I understand this concern. I wonder if that could be solved separately,
> for example by:
> Â - returning int subclasses from AutoField's to_python (a bit like
> str/SafeString for handling escaping)
> Â - not localizing those integers, unless use_l10n is forced (True)
> Does this look
It looks like you went even further than that :D.
Should we still add Q.check() (which will be as you said before), then
refactor BaseConstraint.validate() to use it?
Le mercredi 16 juin 2021 à 02:04:31 UTC+2, charettes a écrit :
> I meant 1. in my previous email where sql.Query.model is allowe
>
> I've gone through the documentation of pymencache and if I'm not wrong its
> nowhere written that it recommends default_noreply to be set to True
>
It's covered in the "best practices" section, which is a list of their
recommendations:
https://pymemcache.readthedocs.io/en/latest/getting_start
