Does CharField still required max_length? Or is it a bug?

2008-08-29 Thread guoqiang qian
hi,all I use django beta2 and find that model's charfield doesn't require max_length parameter anymore. Is there any thing wrong? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post

Re: queryset set difference

2008-08-29 Thread Malcolm Tredinnick
And because I wasn't concentrating about which list I was reading, here comes the obligatory statement: Please take any follow-ups to django-users. This mailing list is for the internal development of Django itself. "How to use" questions should go to the django-users

Re: queryset set difference

2008-08-29 Thread Malcolm Tredinnick
On Fri, 2008-08-29 at 10:51 -0700, ryan wrote: > I have 2 querysets q1 and q2. > > I want q3 = q2-q1, where q3 is a queryset object and contains only the > objects in q2 that are not in q1. > > Is there built in support for this operation? > > The only thing I can think to do is: > list(

queryset set difference

2008-08-29 Thread ryan
I have 2 querysets q1 and q2. I want q3 = q2-q1, where q3 is a queryset object and contains only the objects in q2 that are not in q1. Is there built in support for this operation? The only thing I can think to do is: list( set(q2) - set(q1) ) It doesn't return a queryset, but I can deal with

Re: A (last-minute) compromise on {% url %}

2008-08-29 Thread Eduardo O. Padoan
On Fri, Aug 29, 2008 at 12:43 PM, David Larlet <[EMAIL PROTECTED]> wrote: > > > Le 29 août 08 à 17:18, Jacob Kaplan-Moss a écrit : > >> >> Hi folks -- >> >> While working on some URL-related issues, I ran across a pretty big >> problem with having ``{% url %}`` propagate ``NoReverseMatch`` up into

Re: A (last-minute) compromise on {% url %}

2008-08-29 Thread David Larlet
Le 29 août 08 à 17:18, Jacob Kaplan-Moss a écrit : > > Hi folks -- > > While working on some URL-related issues, I ran across a pretty big > problem with having ``{% url %}`` propagate ``NoReverseMatch`` up into > the templates: if it does that, there's no way to have "optional" > links. The

Re: Recover/Reset password on code.djangoproject.com

2008-08-29 Thread Jacob Kaplan-Moss
On Fri, Aug 29, 2008 at 8:36 AM, Nuno Mariz <[EMAIL PROTECTED]> wrote: > The http://www.djangoproject.com/password_change/ link sent in the > email is broken. http://www.djangoproject.com/accounts/password/change/ Jacob --~--~-~--~~~---~--~~ You received this

Re: Recover/Reset password on code.djangoproject.com

2008-08-29 Thread Nuno Mariz
On Aug 29, 2:23 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote: > http://www.djangoproject.com/accounts/password/reset/ > > Jacob Thanks Jacob, The http://www.djangoproject.com/password_change/ link sent in the email is broken. Nuno --~--~-~--~~~---~--~~ You

Recover/Reset password on code.djangoproject.com

2008-08-29 Thread Nuno Mariz
Hi, I've lost my password on http://code.djangoproject.com, there is a way to recover/reset it? Thanks, Nuno --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send

Re: MultiDb status ?

2008-08-29 Thread Ben Phillips
On Thu, Aug 28, 2008 at 8:18 PM, Rock <[EMAIL PROTECTED]> wrote: > > What you are describing is an edge case for the notion of "sharding" > which is the deployment of identically structured DBs where different > batches of users get saved in different databases. (Flickr does this.) You could

Re: ANN: Django sprint in London, UK - August 30th

2008-08-29 Thread patrickf
Greetings all - Just a quick note to give you the details of the London Sprint tomorrow: Address: 57-61 Mortimer Street, London; Start Time: 10am To gain access, please call me on 077 6840 1800 Any questions - feel free to email me on this address or call me on the number above. See

Re: Django 1.0 and multithreading issues.

2008-08-29 Thread mrts
I am mrts (Mart Sõmermaa). The page was created and updated by me and I'm quite certain the anonymous updates are also mainly by me. So I am entirely to blame for the confusing naming and for any incorrect information. But I do hope that the information is mostly correct and relevant, it is just