This issue has been up with a patch for quite awhile, and wanted to
get some feedback from some devs on this. The fix is pretty simple,
and seems to work ok for me.
Here's my thoughts on it: When I specify ordering with multiple
fields on my Model or my ModelAdmin, the changelist should respe
Thanks for the explanations, but I'm still pretty convinced it may help :)
The initial docs we have from one provider appear to use an API rather than
SMTP apparently. Havn't looked into it yet myself, another one of our dev's
is working on that section. not even sure if we will go with these guys,
On Wed, Sep 2, 2009 at 10:47 AM, Russell
Keith-Magee wrote:
>
> On Wed, Sep 2, 2009 at 2:44 PM, Waldemar Kornewald
> wrote:
>>
>> Hi,
>> why does the backend's query_class() function get the default query
>> class as its parameter? Can't the backend just import BaseQuery? I'm
>> asking because wi
On Wed, Sep 2, 2009 at 2:44 PM, Waldemar Kornewald wrote:
>
> Hi,
> why does the backend's query_class() function get the default query
> class as its parameter? Can't the backend just import BaseQuery? I'm
> asking because with different BaseQuery implementations (for SQL and
> non-SQL) there is
On Wed, Sep 2, 2009 at 6:46 PM, Mat Clayton wrote:
> I'm sure you have this covered but thought I would throw it into the mix. We
> are currently having lots of problems with blacklisting and spam filters
> blocking our email servers, one way we are investigating to avoid this is to
> outsource th
AFAIKT query_class() is only used to set the Query attribute in
django.db.models.sql.query. The relevant code part in sql.query is
# Use the backend's custom Query class if it defines one. Otherwise, use the
# default.
if connection.features.uses_custom_query_class:
Query = connection.ops.que
I'm sure you have this covered but thought I would throw it into the mix. We
are currently having lots of problems with blacklisting and spam filters
blocking our email servers, one way we are investigating to avoid this is to
outsource the email sending to trusted 3rd party services. We don't send
On Tue, Sep 01, 2009 at 11:13:12AM -0700, Jerry Stratton wrote:
> As I'm working with caches, I've found myself wanting to know when the
> cache was created, to compare against the last time some data was
> updated.
Simply using cache.set('your_cache_key', (datetime.now(), your_value)) (or
time()