Re: Ticket 10790 - Things got much worse in Django 1.4

[Phill Tornroth]

Anssi,

Thanks. The comments were helpful and I've looked at the patch enough 
(again, I'm not it's author) that I think I can clean up the comments, 
break out the tests, and do a better job communicating exactly what it's up 
to with around a day's worth of effort. I'm gonna try to fit that into my 
schedule early next week... that is, unless someone else better prepared 
than me speaks up and wants to get involved.

Everything else you said is terrifying.

Phill

On Thursday, August 2, 2012 2:00:58 PM UTC-7, Anssi Kääriäinen wrote:
>
> On 2 elo, 19:17, Phill Tornroth  wrote: 
> > I just submitted a comment about some testing I did that led to 
> discovering 
> > that in 1.4.x, certain queries with null checks in them produce much 
> less 
> > efficient SQL than they did in prior versions. 
> > 
> > A patch that was originally submitted a couple years ago and revised 
> > recently by it's author fixes the original problem (submitted against 
> 1.1) 
> > and the new badness that came along with 1.4.x: 
> > 
> > https://code.djangoproject.com/ticket/10790 
> > 
> > That said, the ticket is really old, so I wanted to see if there are 
> some 
> > non-obvious reasons for resisting moving forward with a merge, and 
> discuss 
> > the possibility of this landing in a 1.4 release as opposed to only on 
> > master. The regression that 1.4.x introduced makes it near impossible 
> for 
> > me to move my project past 1.3.x at the moment, and as I mentioned in 
> the 
> > ticket... this patch ought to speed up lots of queries for basically 
> anyone 
> > with a serious project. 
> > 
> > So... what can I do to help? 
>
> I have added some comments to the ticket. 
>
> Not related to this ticket in particular: the more general problem 
> with ORM fixes is that there seems to be nobody around who understand 
> the ORM completely. The code is complex, and it is hard to see what 
> happens, and especially why things are done in the way they are done. 
> This is the reason why many ORM tickets are stalled - it is really, 
> really hard to see if a patch is correct, as understanding the whole 
> logic in the ORM is so hard. 
>
>  - Anssi 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/A9BKpMHGzJgJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Ticket 10790 - Things got much worse in Django 1.4

[Anssi Kääriäinen]

On 2 elo, 19:17, Phill Tornroth  wrote:
> I just submitted a comment about some testing I did that led to discovering
> that in 1.4.x, certain queries with null checks in them produce much less
> efficient SQL than they did in prior versions.
>
> A patch that was originally submitted a couple years ago and revised
> recently by it's author fixes the original problem (submitted against 1.1)
> and the new badness that came along with 1.4.x:
>
> https://code.djangoproject.com/ticket/10790
>
> That said, the ticket is really old, so I wanted to see if there are some
> non-obvious reasons for resisting moving forward with a merge, and discuss
> the possibility of this landing in a 1.4 release as opposed to only on
> master. The regression that 1.4.x introduced makes it near impossible for
> me to move my project past 1.3.x at the moment, and as I mentioned in the
> ticket... this patch ought to speed up lots of queries for basically anyone
> with a serious project.
>
> So... what can I do to help?

I have added some comments to the ticket.

Not related to this ticket in particular: the more general problem
with ORM fixes is that there seems to be nobody around who understand
the ORM completely. The code is complex, and it is hard to see what
happens, and especially why things are done in the way they are done.
This is the reason why many ORM tickets are stalled - it is really,
really hard to see if a patch is correct, as understanding the whole
logic in the ORM is so hard.

 - Anssi

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: django people: impossible to sign up ?

[Michael]

Ok, I created the issue on githup.


Le jeudi 2 août 2012 21:25:35 UTC+2, Bruno Renié a écrit :
>
> Hi Michael, 
>
> On Thu, Aug 2, 2012 at 9:16 PM, Michael  
> wrote: 
> > Hi, 
> > 
> > Since Django People  is hosted on the djangoproject.com website: 
> > https://people.djangoproject.com/signup/, I thought it would be a good 
> place 
> > to ask my question. If not, sorry for that. 
> > I have an issue to sign up. I actually can't. 
> > I tried with several browsers and when I hit the "sign me up" button, I 
> can 
> > see something is going on but the page is loading again and I have not 
> been 
> > signed up. 
>
> Can you create an issue on the github repo? 
>
> https://github.com/brutasse/djangopeople/issues/new 
>
> If you could include more details using a debugger that'd be great: 
> the failing POST data (obfuscating your password), the actual response 
> if you get any… 
>
> Thanks, 
> Bruno 
>
> > Does anyone have the same issue? 
> > 
> > Thanks. 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Django developers" group. 
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msg/django-developers/-/q4yr7Yax02gJ. 
> > To post to this group, send email to django-developers@googlegroups.com. 
>
> > To unsubscribe from this group, send email to 
> > django-developers+unsubscr...@googlegroups.com. 
> > For more options, visit this group at 
> > http://groups.google.com/group/django-developers?hl=en. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/HccsBBBqTaUJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: django people: impossible to sign up ?

[Bruno Renié]

Hi Michael,

On Thu, Aug 2, 2012 at 9:16 PM, Michael  wrote:
> Hi,
>
> Since Django People  is hosted on the djangoproject.com website:
> https://people.djangoproject.com/signup/, I thought it would be a good place
> to ask my question. If not, sorry for that.
> I have an issue to sign up. I actually can't.
> I tried with several browsers and when I hit the "sign me up" button, I can
> see something is going on but the page is loading again and I have not been
> signed up.

Can you create an issue on the github repo?

https://github.com/brutasse/djangopeople/issues/new

If you could include more details using a debugger that'd be great:
the failing POST data (obfuscating your password), the actual response
if you get any…

Thanks,
Bruno

> Does anyone have the same issue?
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-developers/-/q4yr7Yax02gJ.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

django people: impossible to sign up ?

[Michael]

Hi,

Since Django People   is hosted on the 
djangoproject.com website: https://people.djangoproject.com/signup/, I 
thought it would be a good place to ask my question. If not, sorry for that.
I have an issue to sign up. I actually can't. 
I tried with several browsers and when I hit the "sign me up" button, I can 
see something is going on but the page is loading again and I have not been 
signed up.

Does anyone have the same issue?

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/q4yr7Yax02gJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Ticket 10790 - Things got much worse in Django 1.4

[Phill Tornroth]

I just submitted a comment about some testing I did that led to discovering 
that in 1.4.x, certain queries with null checks in them produce much less 
efficient SQL than they did in prior versions.

A patch that was originally submitted a couple years ago and revised 
recently by it's author fixes the original problem (submitted against 1.1) 
and the new badness that came along with 1.4.x:

https://code.djangoproject.com/ticket/10790

That said, the ticket is really old, so I wanted to see if there are some 
non-obvious reasons for resisting moving forward with a merge, and discuss 
the possibility of this landing in a 1.4 release as opposed to only on 
master. The regression that 1.4.x introduced makes it near impossible for 
me to move my project past 1.3.x at the moment, and as I mentioned in the 
ticket... this patch ought to speed up lots of queries for basically anyone 
with a serious project.

So... what can I do to help?

Thanks in advance,
Phill

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/JOTWVb3Slk4J.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Djonet, the MonetDB backend for Django

[Gijs Molenaar]

Hi Michael,

I see now that most of the Django tests that are still failing seem to be 
forward referencing problems. Django inserts a record to a table with a 
reference to something that doesn't exists (yet). I find it a bit hard to 
debug, since I've not managed to disable transactions while running the 
tests (setting autocommit in the settings file as no effect) and thus can 
not query the database. 

Here is one stacktrace:

"""

/usr/bin/python2.7 /home/gijs/Work/django/tests/runtests.py --settings 
testdjonet.settings --failfast serializers
Creating test database for alias 'default'...
created database in maintenance mode: test_djonet
taken database out of maintenance mode: test_djonet
starting database 'test_djonet'... done
Destroying test database for alias 'default'...
E
==
ERROR: test_forward_refs 
(modeltests.serializers.tests.JsonSerializerTransactionTestCase)
--
Traceback (most recent call last):
  File "/home/gijs/Work/django/tests/modeltests/serializers/tests.py", line 
275, in test_forward_refs
obj.save()
  File "/home/gijs/Work/django/django/core/serializers/base.py", line 165, 
in save
models.Model.save_base(self.object, using=using, raw=True)
  File "/home/gijs/Work/django/django/db/models/base.py", line 551, in 
save_base
result = manager._insert([self], fields=fields, return_id=update_pk, 
using=using, raw=raw)
  File "/home/gijs/Work/django/django/db/models/manager.py", line 203, in 
_insert
return insert_query(self.model, objs, fields, **kwargs)
  File "/home/gijs/Work/django/django/db/models/query.py", line 1576, in 
insert_query
return query.get_compiler(using=using).execute_sql(return_id)
  File "/home/gijs/Work/django/django/db/models/sql/compiler.py", line 910, 
in execute_sql
cursor.execute(sql, params)
  File 
"/home/gijs/Work/monetdb/MonetDB/clients/python/monetdb/sql/cursors.py", 
line 192, in execute
block = self.connection.execute(query)
  File 
"/home/gijs/Work/monetdb/MonetDB/clients/python/monetdb/sql/connections.py", 
line 123, in execute
return self.command('s' + query + ';')
  File 
"/home/gijs/Work/monetdb/MonetDB/clients/python/monetdb/sql/connections.py", 
line 128, in command
return self.mapi.cmd(command)
  File "/home/gijs/Work/monetdb/MonetDB/clients/python/monetdb/mapi.py", 
line 171, in cmd
raise OperationalError(response[1:])
OperationalError: M0M29!INSERT INTO: FOREIGN KEY constraint 
'serializers_article.serializers_article_author_id_fkey' violated


"""


Op maandag 9 juli 2012 17:25:47 UTC+2 schreef Gijs Molenaar het volgende:
>
> Hi Django dev,
>
> I'm working on a MonetDB backend for Django called djonet:
>
> https://github.com/gijzelaerr/djonet
>
> Feel free to test it and let me know if it works for you. I think most 
> stuff  is sort of working, but when I run the Django test suite with a 
> djonet settings some errors pop up that I don't really know yet how to 
> solve.
>
> These problems are:
>  * MonetDB supports a Decimal type with a maximum length of 18 digits.
>  * No support for hyphens in column names
>  * No support for != operation (only <>).
>
> For now I just modified the Django test suite (see attachment), but that 
> doesn't seem to be very constructive. Any suggestion on how to solve these 
> problems?
>
> thanks,
>
>  - Gijs
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/_ZFllhucA68J.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Django 1.4.x support for Firebird

[Anssi Kääriäinen]

It seems there is need for "max decimal digits" feature or something
like that, so that one can skip the failing tests... Please file a
ticket.

 - Anssi

On 2 elo, 09:29, mariuz  wrote:
> We need your opinions , patches ideas
>
> https://groups.google.com/forum/?fromgroups#!topic/django-firebird-de...
>
> ps: yes we moved to github

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Django 1.4.x support for Firebird

[mariuz]

We need your opinions , patches ideas  

https://groups.google.com/forum/?fromgroups#!topic/django-firebird-dev/SUXh2Jpwgnc

ps: yes we moved to github

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/I56Ixdb5h24J.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.