Re: Database pooling vs. persistent connections

One question: does this proposal include some way of specifying a maxiumum number of outstanding connections to the database from a single process? Looked but didn't see it in the pull request. In my experience, most PostgreSQL instances don't have a whole lot of breathing room in terms of th

Re: auth.user refactor: the profile aproach

(e.g. 'user') and any other user-domain-specific customizations needed. Thanks, Eric Florenzano > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google

Re: jQuery.tmpl() and Django

On May 26, 11:59 pm, Jonathan Slenders wrote: > +1 for the verbatim tag. I think this is something that we need in > Django by default. > > But I think that ericflo his implementation is not truly verbatim. I > mean, that it will probably drop whitespace between "{%" and the tag > names. It may no

Re: NoSQL support

seemingly unrelated changes in there having to do with password resetting, base64 url encoding, and file uploading--none of which have to do with NoSQL. Thanks, Eric Florenzano -- You received this message because you are subscribed to the Google Groups "Django developers" group. To

Re: Proposal: Tutorial Refresh

k that I had was that people liked being able to download the whole source tree. Hrm, I feel like I have more battle scars, but right now I can't think of anything else. I'll be around so feel free to ask me any questions or whatever. Thanks, Eric Florenzano --~--~-~--~--

Re: Model.objects.raw() (#11863)

utside of Django than inside of it. That being said, this proposal is actually something that I think fits well within Django core itself, as it really is a logical extension of the core functionality of the ORM. Thanks, Eric Florenzano --~--~-~--~~~---~--~~ You

Re: Adding signing (and signed cookies) to Django core

A big +1 on signed cookies, and I like the direction the discussion is going. Also, I hope this doesn't derail this discussion, but I hope after signed cookies are added, auth can be made to optionally use signed cookies instead of sessions. Thanks, Eric Flore

Re: Proposal for 1.2: built-in logging with django.core.log

On Sep 17, 1:25 am, Simon Willison wrote: > 1. We'll be able to de-emphasise the current default "e-mail all > errors to someone" behaviour, which doesn't scale at all well. I'm a big fan of this proposal, for exactly this reaso

Re: #9282 (comment moderation features) and Akismet removal

s > just leaving the door open for more additions in the future. I don't really understand this argument. Maybe I'm not parsing it correctly, but I read this as "Your implementation is good, but let's not add it now so that we can add it later", whic

Re: Proposal: enable CSRF middleware by default

It took me a bit to realize that it had to do with the CSRF middleware, and if it tripped me up, it's going to trip up other users as well. If we're going to ship CSRF middleware on by default, I propose that we take a second look at the wontf

Re: Multiple Database API proposal

He's got a +1 from me (not that it means much now that I'm on Malcolm's special list). Speaking of Malcolm's special list... > One suggestion Eric Florenzano had was that we go above and beyond > just storing the methods and parameters, we don't even excecute them &

Re: WTForm should be inbuilt to Django, and make admin & others use it.

If anyone else read this and was as confused as I was at first, make sure to note that this is different than WTForms[1], which is an alternate form library that took several of its cues from Django's newforms. [1] http://wtforms.simplecodes.com/ Thanks, Eric Flore