On Monday, March 25, 2013 6:58:12 AM UTC-4, Tim Chase wrote:
>
> I can only speak for testing IN-vs-EXISTS speed on MSSQLServer at
> $OLD_JOB, but there it's usually about the same, occasionally with IN
> winning out.
In SQL 2008r2, the optimizer is usually smart enough to end up with the
s
Previous discussion (which I've read before):
https://code.djangoproject.com/ticket/16774
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developer
What action, if any, do you suggest I take now?
On Tuesday, March 26, 2013 2:42:11 PM UTC+11, Ramiro Morales wrote:
>
> On Tue, Mar 26, 2013 at 12:36 AM, meric >
> wrote:
> > Thanks, I'll reply to that thread. I posted my proposal 6 months before
> that
> > post, would've been nice if they pos
I've previously raised this idea and created a pull request.
https://github.com/django/django/pull/378
The problem with creating with a catch all view:
You have following models:
Country, Industry, Company, School.
You want to have the following kinds of urls:
//
// /
///
///
/ /
//
On Tue, Mar 26, 2013 at 12:36 AM, meric wrote:
> Thanks, I'll reply to that thread. I posted my proposal 6 months before that
> post, would've been nice if they posted in my thread...
Jacob voted in favor of the feature (on the #16774 [1]ticket) and Adrian
voted -1 on that thread. But they were
Thanks, I'll reply to that thread. I posted my proposal 6 months before
that post, would've been nice if they posted in my thread...
On Tuesday, March 26, 2013 2:33:14 PM UTC+11, Ramiro Morales wrote:
>
> On Tue, Mar 26, 2013 at 12:28 AM, meric >
> wrote:
> > I have made a pull request for djan
On Tue, Mar 26, 2013 at 12:28 AM, meric wrote:
> I have made a pull request for django 6 months ago, but it doesn't seem to
> be getting much response so far.
>
> What can I do to get more feedback as to what's wrong with it, and try to
> get it accepted?
>
> Here is the pull request:
>
> https://
I have made a pull request for django 6 months ago, but it doesn't seem to
be getting much response so far.
What can I do to get more feedback as to what's wrong with it, and try to
get it accepted?
Here is the pull request:
https://github.com/django/django/pull/378
--
You received this mess
Previous discussion:
https://groups.google.com/forum/?fromgroups=#!searchin/django-developers/dynamic$20sites/django-developers/QSXLGSxy7Vk/TxgiJzz5nd8J
https://code.djangoproject.com/ticket/16983
https://code.djangoproject.com/ticket/4438
My proposal allows getting the current site based on requ
On Tue, Mar 26, 2013 at 1:49 AM, Bharadwaj Desikan
wrote:
> Hi
>
> I am new to Django Contributors but have quite a good expertise in python..
>
> I have assigned ticket https://code.djangoproject.com/ticket/6103 to
> myself.. So the current tests are stable for
> which Django Release.
>
> Betwee
And fixed
On Monday, March 25, 2013 10:06:21 PM UTC+1, Florian Apolloner wrote:
>
> Hi,
>
> I updated jenkins today and ran into a major issue (
> https://issues.jenkins-ci.org/browse/JENKINS-17337). This will be fixed
> in a few hours and I'll update jenkins tomorrow.
>
> Sorry for the inconveni
Hi,
I updated jenkins today and ran into a major issue
(https://issues.jenkins-ci.org/browse/JENKINS-17337). This will be fixed in
a few hours and I'll update jenkins tomorrow.
Sorry for the inconvenience.
Regards,
Florian
--
You received this message because you are subscribed to the Google
Le samedi 23 mars 2013 22:28:31 UTC+1, Claude Paroz a écrit :
>
> Le samedi 23 mars 2013 12:16:15 UTC+1, Evgeny a écrit :
>>
>> Hi.
>>
>> Is it necessary to cast help_text to string in Field.__init__ there
>> https://github.com/django/django/blob/master/django/forms/fields.py#L92 ?
>> I will be e
On 25 mars 2013, at 20:20, Stephen Burrows wrote:
> django-nose is pretty useful for handling test discovery issues, if you're
> looking for a quick fix.
I don't suffer from this problem because I use a custom test runner to avoid
it. My goal here is to improve the framework for others.
Thes
The tests are nested whether they're in the core tests or in contrib.
Philosophically this is more a question of coding at a distance. Putting
the tests in /tests makes it less obvious which app they actually belong
to. Additionally, I'd see the fact that it would be impossible to use
manage.py
On 25 March 2013 12:37, Anssi Kääriäinen wrote:
> I feel pretty strongly that NOT EXISTS semantics are wanted. The NOT
> IN semantics are likely there just because that is how the
> implementation was originally done, not because there was any decision
> to choose those semantics.
Most likely, y
It seems like it could be a dangerous precedent to cater to people who
don't take the time to fully read the docs, but in this case I'm a bit
sympathetic. On the other hand, this example will probably be a bit more
obvious when we drop support for Python 2.6 and no longer have
django.utils.unit
Hi
I am new to Django Contributors but have quite a good expertise in python..
I have assigned ticket https://code.djangoproject.com/ticket/6103 to
myself.. So the current tests are stable for
which Django Release.
Between which commits I should take diff .. This will help me to summarize
With the change to HttpResponse made in Django 1.5, I'm finding that in my
code, which caches a generated response, results in an empty body when that
page is requested a second time. The first time the page is requested, it
is not in the cache, and the page is generated normally and added to th
I have no idea how EXISTS performs on MySQL, however I can say that IN +
subqueries on MySQL are so atrocious that we outright banned that where I
work, so I don't see how it could be worse :)
Alex
On Mon, Mar 25, 2013 at 8:37 AM, Anssi Kääriäinen
wrote:
> On 25 maalis, 13:23, Simon Riggs wrot
On 25 maalis, 13:23, Simon Riggs wrote:
> On 25 March 2013 10:58, Tim Chase wrote:
>
> > On 2013-03-25 03:40, Anssi Kääriäinen wrote:
> >> I am very likely going to change the ORM to use EXISTS subqueries
> >> instead of IN subqueries. I know this is a good idea on PostgreSQL
> >> but I don't hav
On 25 March 2013 10:58, Tim Chase wrote:
> On 2013-03-25 03:40, Anssi Kääriäinen wrote:
>> I am very likely going to change the ORM to use EXISTS subqueries
>> instead of IN subqueries. I know this is a good idea on PostgreSQL
>> but I don't have enough experience of other databases to know if
>>
On 2013-03-25 03:40, Anssi Kääriäinen wrote:
> I am very likely going to change the ORM to use EXISTS subqueries
> instead of IN subqueries. I know this is a good idea on PostgreSQL
> but I don't have enough experience of other databases to know if
> this is a good idea or not.
I can only speak fo
I am very likely going to change the ORM to use EXISTS subqueries
instead of IN subqueries. I know this is a good idea on PostgreSQL but
I don't have enough experience of other databases to know if this is a
good idea or not.
There are two main reasons for doing this. First, exists should
perform
24 matches
Mail list logo
