Re: BlobField before .97

David Cramer wrote: > In my opinion BlobField's need some kind of support inside of Django > before the coming of 0.97 release. > > They have never been officially supported, but they were at least > usable (as say a TextField) before Unicode. Now they're unusable as > you run into encoding/decod

Re: Design Decision: Dynamic settings.SITE_ID (ref. #4438)

I just made a ticket (http://code.djangoproject.com/ticket/5022) that *might* resolve some issues for certain subdomain situations. I would love to hear any feedback, good or bad. Thanks! -Tom --~--~-~--~~~---~--~~ You received this message because you are subscr

full Atom Publishing Format support almost done

As described here[1], I finally got around to working on improving django support for the Atom Publishing Format. There's been a ticket [2] for this since PyCon but yesterday I started a Google Code project and now I'm mostly done. Equivalents to django.contrib.syndication.feeds.Feed, djan

Re: ticket #2101: maxlength should be max_length

Thanks for updating, Gary. I was letting it slide until after newforms- admin hit. Good to see it's got a committer champion now ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post

BlobField before .97

In my opinion BlobField's need some kind of support inside of Django before the coming of 0.97 release. They have never been officially supported, but they were at least usable (as say a TextField) before Unicode. Now they're unusable as you run into encoding/decoding issues. --~--~-~--

Re: ticket #2101: maxlength should be max_length

On 7/30/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > That sounds like the best thing to do -- I don't see a huge need to > deprecate maxlength immediately, or even issue warnings about it. The > change gets a +1 from me. I'd say that making maxlength issue a PendingDeprecationWarning -- which

Re: ticket #2101: maxlength should be max_length

On 7/30/07, Gary Wilson <[EMAIL PROTECTED]> wrote: > The patch actually still keeps maxlength around, raising an error only > if both max_length and maxlength are used. Currently, there is no > warning if maxlength is used, but that could be added. That sounds like the best thing to do -- I don'

Re: ticket #2101: maxlength should be max_length

Jacob Kaplan-Moss wrote: > Seems that making the change outright would annoy a whole host of > people... IIRC, we'd decided to deprecate max_length and issue > warnings... does that sound right? The patch actually still keeps maxlength around, raising an error only if both max_length and maxlengt

Ticket #3700: XhtmlDegraderMiddleware

Hello, A while back I wrote some middleware to improve XHTML usage . Is this something that could or should be included within Django? XHTML is ideally sent with the application/xhtml+xml media type; however it's normally delivered as text/html beca

Re: ticket #2101: maxlength should be max_length

On 7/30/07, Gary Wilson <[EMAIL PROTECTED]> wrote: > I brought the patch back in sync with trunk, and would like to make a > call for some eyes, as this is a big, mostly boring, patch. I don't > want to let this one get 6 months out of date again :) Someone remind me -- did we decide what we wan

ticket #2101: maxlength should be max_length

I brought the patch back in sync with trunk, and would like to make a call for some eyes, as this is a big, mostly boring, patch. I don't want to let this one get 6 months out of date again :) Thanks, Gary --~--~-~--~~~---~--~~ You received this message because y

Re: ticket 4789: select_related + depth bug, apply the patch?

On Mon, 2007-07-30 at 16:11 +0200, Gábor Farkas wrote: > Jacob Kaplan-Moss wrote: > > On 7/30/07, Gábor Farkas <[EMAIL PROTECTED]> wrote: > >> approximately when do you plan to finish this rewrite? i realize it's > >> hard to predict, i'm just asking for very rough estimates... are we > >> talking

select_related additions

I have taken a bit of time to rewrite part of the QuerySet code (including select_related). Please, no lectures about a QuerySet refactoring. The changes force .filter() to take advantage of select_related. Before: .filter(mykey__name='Hello') would give you results, but if you didn't do .select

Re: Simple Aggregation

Hello, I know that that's the case, and each proposal for that aggregation feature looks better than the last! But, in the interim, there's this. Also, this is denormalized, so it may even useful for performance reasons after the aggregation framework is completed. (Why compute SUM(some list) e

Re: ticket 4789: select_related + depth bug, apply the patch?

Jacob Kaplan-Moss wrote: > On 7/30/07, Gábor Farkas <[EMAIL PROTECTED]> wrote: >> approximately when do you plan to finish this rewrite? i realize it's >> hard to predict, i'm just asking for very rough estimates... are we >> talking about days or weeks or months? > > As a general rule we don't g

Re: ticket 4789: select_related + depth bug, apply the patch?

On 7/30/07, Gábor Farkas <[EMAIL PROTECTED]> wrote: > approximately when do you plan to finish this rewrite? i realize it's > hard to predict, i'm just asking for very rough estimates... are we > talking about days or weeks or months? As a general rule we don't give time estimates. Seems the best

Re: Simple Aggregation

On 7/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hello, > > Today I spun off the (simplistic) aggregation features of a site that > I'm building and made it a generic app. Hi Eric, Aggregation is a feature that has been planned for Django for some time. It's actually the reason I sta

Simple Aggregation

Hello, Today I spun off the (simplistic) aggregation features of a site that I'm building and made it a generic app. It's useful for keeping track of certain kinds of counting and summing, etc. (especially if count(*) is O(n) for your database engine, this brings that down to O(1)). For example

Re: development documentation

> Marc Garcia wrote: >> Is there any django development documentation? I couldn't find any >> document on how to start writting my own django add-on. Russell Keith-Magee wrote: > All the documentation that exists is either in the Django source tree > under /docs (which is what is displayed at

Re: ticket 4789: select_related + depth bug, apply the patch?

Malcolm Tredinnick wrote: > On Fri, 2007-07-27 at 08:55 +0200, Gábor Farkas wrote: >> hi, >> >> ticket 4789 fixes a bug in select_related-queries when used with the >> depth parameter. >> >> it contains a patch which fixes the problem. it also contains the tests >> for this fix. >> >> without th