Re: #12801 : Allow empty non-nullable ForeignKey fields until save()

Thank you, Tamas. Yes, that's what I mean. Without you I might have come to believe that something is wrong with my brain... And yes, I can live with it. It's just a pity that others will stumble on it just because it isn't documented. Luc On 10.02.2010 19:30, Tamas Szabo wrote: > Hi, > >

Re: QuerySet.exists() - Possible bug?

MySQL, in this situation, would have to actually select a row to return a result, so it's slower. If it was just select 1 as a from table where indexed_value = N, it doesn't even hit the tables, just the indexes. It's definitely not more efficient, and probably just an oversight somewhere. On

Re: Bug in Form metaclass?

Thanks for looking into this Russ > Firstly, django-dev isn't "second tier tech support" - if you don't > get an answer on django-users for a user-space question, that's a > pity, but it doesn't mean you can or should "escalate" to django-dev. I realise this; I thought this was the place to

Re: Translation policy - clarification required?

On Thu, Feb 11, 2010 at 8:10 AM, Alex Gaynor wrote: > On Wed, Feb 10, 2010 at 7:07 PM, Russell Keith-Magee > wrote: >> Hi all, >> >> I need some feedback/assistance from those with experience with the >> translation tool set. >> >> Karen Tracey just

Re: Bug in Form metaclass?

On Thu, Feb 11, 2010 at 7:40 AM, Simon Meers wrote: > Disclaimer: Just in case this was a naive mistake on my part, I posted > this on django-users first [1] and posed the question several times on > #django, but have received no answers. Firstly, django-dev isn't "second tier

Re: Status of branch soc2009/http-wsgi-improvements? (and ticket 2131)

On Wed, Feb 10, 2010 at 11:09 PM, Jari Pennanen wrote: > Hi! > > I was wondering what is the status of branch branches/soc2009/http- > wsgi-improvements ( > http://github.com/django/django/tree/soc2009/http-wsgi-improvements > )? I'm personally interested one bug it

Re: Translation policy - clarification required?

On Wed, Feb 10, 2010 at 7:07 PM, Russell Keith-Magee wrote: > Hi all, > > I need some feedback/assistance from those with experience with the > translation tool set. > > Karen Tracey just pointed out that I may have made a booboo with the > handling of translations in the

Translation policy - clarification required?

Hi all, I need some feedback/assistance from those with experience with the translation tool set. Karen Tracey just pointed out that I may have made a booboo with the handling of translations in the 1.1.X branch. I committed updates to trunk for the no, fr, nl, sk, cz and ro translations. I

Re: What The Enterprise wants from Django

On 19.01.2010 23:26, Jacob Kaplan-Moss wrote: > Finally, we ruminated over the difficulties in building rich internet > applications. Sure, writing HTML/CSS/JS/Python/SQL by hand works fine, > but we doesn't really have a good answer for the people who want > something IDE or GUI-ish. Meanwhile,

Bug in Form metaclass?

Disclaimer: Just in case this was a naive mistake on my part, I posted this on django-users first [1] and posed the question several times on #django, but have received no answers. # # forms.py:

Re: Add Mod(%) Operator to If Tag

On Wednesday 10 February 2010 19:00:47 Jonas Obrist wrote: > I'm not sure if this was discussed before, but what about allowing > to easily register custom comparison operators? I'm thinking of a > similar API we currently have for registering template > tags/filters for if-tag operators. My

Re: contrib.Auth

I think that an easy way to define your own user model is better idea. Auth app should be more generic. It should define a protocol for user, group and permission objects (and of course there should be back compatible implementation of this protocols used by default). There is a ticket about

Re: Status of branch soc2009/http-wsgi-improvements? (and ticket 2131)

Hi, On Wed, Feb 10, 2010 at 11:09:29AM -0800, mrts wrote: > On Feb 10, 5:24 pm, Tom Evans wrote: > > On Wed, Feb 10, 2010 at 3:09 PM, Jari Pennanen > > wrote: > > > Hi! > > > > > I was wondering what is the status of branch

Re: Status of branch soc2009/http-wsgi-improvements? (and ticket 2131)

On Feb 10, 5:24 pm, Tom Evans wrote: > On Wed, Feb 10, 2010 at 3:09 PM, Jari Pennanen > wrote: > > Hi! > > > I was wondering what is the status of branch branches/soc2009/http- > > wsgi-improvements > >

Re: Add Mod(%) Operator to If Tag

Alex Gaynor wrote: On Wed, Feb 10, 2010 at 12:10 PM, megaman821 wrote: Since Django 1.2 is not out yet I have been using the smart_if tag in all my projects, with one addition. Since I believe the new if tag is based on the smart_if tag code on Django Snippets, I want

Re: #12801 : Allow empty non-nullable ForeignKey fields until save()

Hi, Well, I'm not a django core developer, so my post probably won't weight that much, but I can't leave Luc with the feeling that that aren't other people that have the same opinion as him. Luc, I'm with you on this one :) First of all the problem is in an area of handling the mismatches

Add Mod(%) Operator to If Tag

Since Django 1.2 is not out yet I have been using the smart_if tag in all my projects, with one addition. Since I believe the new if tag is based on the smart_if tag code on Django Snippets, I want to propose adding the mod(%) operator to it. Often I have display logic where I am displaying a

Re: Status of branch soc2009/http-wsgi-improvements? (and ticket 2131)

On Wed, Feb 10, 2010 at 3:09 PM, Jari Pennanen wrote: > Hi! > > I was wondering what is the status of branch branches/soc2009/http- > wsgi-improvements ( > http://github.com/django/django/tree/soc2009/http-wsgi-improvements > )? I'm personally interested one bug it

Status of branch soc2009/http-wsgi-improvements? (and ticket 2131)

Hi! I was wondering what is the status of branch branches/soc2009/http- wsgi-improvements ( http://github.com/django/django/tree/soc2009/http-wsgi-improvements )? I'm personally interested one bug it fixes, mainly ticket #2131 ( http://code.djangoproject.com/ticket/2131 ) The branch seems to be

Re: #12801 : Allow empty non-nullable ForeignKey fields until save()

Thank you, Henrique, for dropping in. As I said earlier, I don't want to bother the community with my stubbornness or whatever it may be, so feel free to STOP READING HERE if there is danger that this topic wastes your time. But to be honest, I must unfortunately say that I disagree also with

Re: QuerySet.exists() - Possible bug?

On Wed, Feb 10, 2010 at 2:05 AM, Karen Tracey wrote: ... >>  * What version of Django (including SVN revision, if appropriate) are >> you using? > > I tried current trunk and backed off to the changeset where the function was > added -- query was the same.  Looking at the

Re: #12801 : Allow empty non-nullable ForeignKey fields until save()

Thanks, Karen, for your explanations which are very clear. I accept the community's decision and won't bother you any longer. And maybe one day I will even understand why this behaviour is not odd. Luc On 9.02.2010 17:03, Karen Tracey wrote: > On Tue, Feb 9, 2010 at 3:02 AM, Luc Saffre

Re: Admin refactoring

On Wed, Feb 10, 2010 at 6:41 PM, PauloS wrote: > Currently it is easy to change the template engine in a Django > project, but if you change the ORM layer you lost the whole Admin > thing, the very app that made Django so special. > > If we are talking about refactoring

Re: Admin refactoring

On Wed, 2010-02-10 at 02:41 -0800, PauloS wrote: > If we are talking about refactoring Admin code (not only html/css > stuff), do you guys think it can be more decoupled from Django ORM? How so? > Is it possible to design some abstraction middleware to loose the bond > between admin and Django

Admin refactoring

Currently it is easy to change the template engine in a Django project, but if you change the ORM layer you lost the whole Admin thing, the very app that made Django so special. If we are talking about refactoring Admin code (not only html/css stuff), do you guys think it can be more decoupled

Re: contrib.Auth

Good suggestions, I think removing username and email from the user might be a good idea. Right now I authenticate with the email address stored on the profile and the username is a random hash :) As for breaking data and migrations; it shouldn't be that hard to write a management command that

Re: QuerySet.exists() - Possible bug?

On Wed, Feb 10, 2010 at 2:22 AM, Russell Keith-Magee wrote: > It certainly doesn't look right; .exists() should be faster than > .count(), and having all the extra columns in the query looks a little > weird. > > However, to say for sure, we need a few more details: > >