On Thu, 2008-11-20 at 07:20 +0300, Ivan Sagalaev wrote:
> Malcolm Tredinnick wrote:
> > Okay. If we go this path, it's something to include in Django, rather
> > than recommending yet another caching package. We either make it a
> > configuration option to force python-memcache or cmemcache or we
Malcolm Tredinnick wrote:
> Okay. If we go this path, it's something to include in Django, rather
> than recommending yet another caching package. We either make it a
> configuration option to force python-memcache or cmemcache or we just
> "Do The Right Thing", with the latter being preferable.
Malcolm Tredinnick wrote:
[...]
> Hopefully, MySQL will fix their bug one day. That's the way to resolve
> this.
>
Just so long as nobody holds their breath waiting ...
regards
Steve
--
Steve Holden+1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
Ok, I understand what you are saying now, and I hadn't thought about it
the way you present it. Thanks.
Apaar
-Original Message-
From: django-developers@googlegroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Malcolm
Tredinnick
Sent: Wednesday, November 19, 2008 7:00 PM
To: django-deve
On Nov 20, 2008, at 00:55, Malcolm Tredinnick wrote:
> Okay. If we go this path, it's something to include in Django, rather
> than recommending yet another caching package. We either make it a
> configuration option to force python-memcache or cmemcache or we just
> "Do The Right Thing", with the
On Wed, 2008-11-19 at 15:41 -0800, Apaar Trivedi wrote:
[...]
> But how about at least introducing some way to suppress the order_by
> column being added to the select fields? This way postgres is still
> supported, and mysql distinct will work as well.
I'm strongly against this. We should be f
On Thu, 2008-11-20 at 00:46 +0100, Ludvig Ericson wrote:
> On Nov 20, 2008, at 00:11, Malcolm Tredinnick wrote:
> > That's possible. The hash function in the pure-Python memcached
> > wrapper
> > is replaceable (it's an attribute), so I was looking at replacing it
> > with the version from cmem
I know this is a topic you all may have discussed a number of times,
but I feel I need to bring it up still. I noticed that when doing an
order_by, the column name is implicitly added to the select. However,
this causes a problem when doing a distinct, as well.
Consider that someone is selectin
On Nov 20, 2008, at 00:11, Malcolm Tredinnick wrote:
> That's possible. The hash function in the pure-Python memcached
> wrapper
> is replaceable (it's an attribute), so I was looking at replacing it
> with the version from cmemcached. Using a third hashing algorithm
> would
> be a bit silly,
On Wed, 2008-11-19 at 03:26 -0800, taleinat wrote:
[...]
> What about having Django's memcached cache backend implement its own
> hashing algorithm? This could be the "standard" one used in
> libmemcache and cmemcache, or perhaps a consistent hashing algorithm
> [1] such as libketama[2].
That's
Shao:
This is a very general question, and is only indirectly connected to
Django, since the task could be performed in most web frameworks.
However, the django-dev list is reserved to discussions about the
development *of* Django.
For questions about development *with* Django you should address
On Nov 19, 2008, at 12:26, taleinat wrote:
> What about having Django's memcached cache backend implement its own
> hashing algorithm? This could be the "standard" one used in
> libmemcache and cmemcache, or perhaps a consistent hashing algorithm
> [1] such as libketama[2].
As I said in the tick
Adrian,
I think this reorganization of Django's documentation is a Big Step Forward.
Congratulations. Not only this will be very important for Django adoption
and public consideration, but also it will model other systems'
documentation, methinks.
best,
haroldo
On Tue, Nov 18, 2008 at 5:44 AM,
Dear ALL,
I am very much interested in using a HTML to fire off a data
processing script to run over the internet.
I will be very grateful if you can advise me on passing parameters
from an HTML form to a script and fire the script off to carry out
full execution, monitor its progress and return
You guys are really bad about keeping on topic. :)
On Wed, Nov 19, 2008 at 9:32 AM, Joey Wilhelm <[EMAIL PROTECTED]> wrote:
> Hanne,
>
> I ran into that exact problem myself and filed the following ticket related
> to the issue: http://code.djangoproject.com/ticket/9519
>
> I also found that you
Hanne,
I ran into that exact problem myself and filed the following ticket related
to the issue: http://code.djangoproject.com/ticket/9519
I also found that you could run your own delete operation through the ORM,
however, to work around this. It's more work and certainly not in line with
DRY or
Actually, this is a typical URL from Google:
1. Search "django models"
2. Get
http://docs.djangoproject.com/en/dev/ref/models/instances/?from=olddocs
IMHO, the correct solution is an actual 301 (permanent) redirect to take
Google and others where the "current" URL of the page is. Unfortunately
On Mon, Nov 17, 2008 at 00:55, Frank Liu <[EMAIL PROTECTED]> wrote:
> Plus, if you had a chance to look at the type of databases that I have
> to deal with by day, you will see why this is so important to me.
Yo. Not that big, but there's a DBA involved for some of 'em. Let's
just say I can't use
On Oct 8, 10:54 am, Malcolm Tredinnick wrote:
> On Wed, 2008-10-08 at 10:37 +0200, Ludvig Ericson wrote:
> > Hello,
> > I had issues with Django opting to use cmemcache and secondarily
> > python-memcached.
>
> > This behavior is extremely dangerous-- lest you be aware, cmemcache
> > and pytho
19 matches
Mail list logo
