Re: Using dimension_fields in models.ImageField cause performance penalties

Thank Russ, I have opened a ticket : http://code.djangoproject.com/ticket/15817 Unfortunately, I can't find a easy way to solve the problem because the solution is somewhere in the ImageFileDesciptor.__set__() method which is a dangerous area ! Cordialement, Stanislas. On Apr 12, 2:03 pm,

Needed support to delete specialization , while preserving base class instance (multi-table inheritance)

This ticket explains everything: http://code.djangoproject.com/ticket/15579 In short: I issued a ticket on this topic and russellm has closed it with "it's already working" explanation. I checked it again and it looks like this feature is indeed not supported or I'm doing it wrong. Please verify

Re: Needed support to delete specialization , while preserving base class instance (multi-table inheritance)

On Wed, Apr 13, 2011 at 7:45 PM, Piotr Czachur wrote: > This ticket explains everything: http://code.djangoproject.com/ticket/15579 > > In short: > I issued a ticket on this topic and russellm has closed it with "it's > already working" explanation. I checked it again and it

Request for comments: custom admin filters

Hello there, I've just posted a patch with a suggested implementation of custom admin filters: http://code.djangoproject.com/attachment/ticket/5833/5833.custom-filterspecs.3.diff I've written some pretty comprehensive tests and have also had a stab at writing some documentation. You should find

Re: Request for comments: custom admin filters

Hi Julien -- Thanks for your work on this! I'm working my way through the patch, and it's looking good. I'm pretty happy with the internals, though I do have some questions about the public API: * I'm rather unhappy with the `SimpleListFilter`/`FieldListFilter` breakdown, and especially the way

Error importing template source loader when upgrading from r15883 to r16025

Hello, I have a small web site that was running happily with django r15883 that I updated March 21st. Yesterday I upgraded to the latest version (r16025) and then I'm getting an error that 505s my site: Error importing template source loader

Re: Error importing template source loader when upgrading from r15883 to r16025

On 13 April 2011 18:37, lazyant wrote: > Hello, > > I have a small web site that was running happily with django r15883 > that I updated March 21st. > > Yesterday I upgraded to the latest version (r16025) and then I'm > getting an error that 505s my site: > > Error

Re: Request for comments: custom admin filters

Hi Julien, Thanks for working on this! Will your patch simplify creating filters not based on choices? E.g. min/max filters where exact minimun and maximum values can be entered (using form with method=GET and input fields for values)? I want a pony ;) It would also be good to make

Re: Error importing template source loader when upgrading from r15883 to r16025

On Wed, Apr 13, 2011 at 1:37 PM, lazyant wrote: > Hello, > > I have a small web site that was running happily with django r15883 > that I updated March 21st. > > Yesterday I upgraded to the latest version (r16025) and then I'm > getting an error that 505s my site: > >

Re: RFC #2705 (Support for SELECT FOR UPDATE)

Hi, Sorry to bump this one again. Now 1.3's out the door, I'd like this to be looked at again, if possible. http://code.djangoproject.com/ticket/2705 I'll re-apply Ramiro's patch locally and make sure everything still checks out for me, and report back. The latest version of the patch

Re: Error importing template source loader when upgrading from r15883 to r16025

Hi, Thanks for the quick answers. I fixed the problem by changing in settings.py TEMPLATE_LOADERS: 55 55 TEMPLATE_LOADERS = ( 56 - 'django.template.loaders.filesystem.load_template_source', 57 -

Re: RFC #2705 (Support for SELECT FOR UPDATE)

On Wed, Apr 13, 2011 at 2:08 PM, Dan Fairs wrote: > However, > it's worth mentioning that the Oracle tests seemed to be mostly broken in > the first place, with dozens of errors. Thanks for following up on those. I reviewed the Oracle tests shortly before the 1.3 release

Re: Request for comments: custom admin filters

Hi Mikhail, On Apr 14, 4:56 am, Mikhail Korobov wrote: > Will your patch simplify creating filters not based on choices? E.g. > min/max filters where exact minimun and maximum values can be entered > (using form with method=GET and input fields for values)? I want a >

Re: combining querysets with isnull

On Thursday, October 14, 2010 7:03:35 PM UTC-4, Johannes Dollinger wrote: > > > Am 14.10.2010 um 23:07 schrieb Dan Watson: > > > There seems to be some inconsistent behavior when combining querysets > > that use isnull on a ForeignKey. I'm not sure how to explain it well > > in plain english, so

Re: Request for comments: custom admin filters

On Apr 14, 3:11 am, Jacob Kaplan-Moss wrote: > Hi Julien -- > > Thanks for your work on this! I'm working my way through the patch, > and it's looking good. I'm pretty happy with the internals, though I > do have some questions about the public API: > > * I'm rather unhappy

Tying log messages from a single request together?

Hi, Is there an idiomatic way to tie messages from a single request together with 1.3's new logging features? From the documentation it doesn't look like there is. Something like what drlog does ( http://fairviewcomputing.com/blog/2008/03/05/django-request-logging/). It seems like a standard

Re: Request for comments: custom admin filters

On Apr 14, 8:46 am, Julien Phalip wrote: > Thanks a lot for your feedback. I agree with all your points and have > made the corresponding amendments in a new > patch:http://code.djangoproject.com/attachment/ticket/5833/5833.custom-filt... Sorry, just in case you've already