Re: [Django] #9554: select related - maximum depth

[Django]

#9554: select related - maximum depth
---+
  Reporter:  gert  | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Contrib apps  |   Version:  1.0   
Resolution:|  Keywords:  select related
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by gert):

 ramiro: yes, I only picked it up in the admin contrib app. At that stage I
 was unaware of the depth=X parameter. I think it adequately addresses the
 issue for custom applications, also I don't think internally
 select_related needs to drop the 5 down to 3.


 BUT, for the admin application I think a tweak is required. Arguments for
 explicitly lowering select_related for admin to say 3 :) are;

 1) Whatever value you take must hit the sweat spot for 90% of situations
 otherwise it will slow down rather than increase overall application
 speed. I can not even think of an example where I want to go down 5
 levels. (object.level1.level2.level3.level4.level5)

 2) Remember that the effect on the database increases exponentially, e.g.

 3 levels 2 references per object => 3^2^ = 9 DB tables

 5 levels 2 references per object => 5^2^ = 25 DB tables

 5 levels 3 references per object => 5^3^ = 125 DB tables

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9880: Spaces in assignment of values of named parameters for 'url' template function raise 'TypeError'

[Django]

#9880: Spaces in assignment of values of named parameters for 'url' template
function raise 'TypeError'
--+-
  Reporter:  Art Skvira   | Owner:  
nobody
Status:  closed   | Milestone:  
  
 Component:  Uncategorized|   Version:  1.0 
  
Resolution:  invalid  |  Keywords:  
  
 Stage:  Unreviewed   | Has_patch:  0   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Comment (by ubernostrum):

 Because of the way Django's template system works, spaces are taken to be
 separators between arguments. Remember: things you type into templates are
 not directly interpreted as Python code, and the template language has its
 own, different-from-Python, ideas about what is and is not acceptable
 syntax.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7150: patch to implement view pemission in admin

[Django]

#7150: patch to implement view pemission in admin
+---
  Reporter:  Antonio Gallo   | Owner:  
nobody   
Status:  closed | Milestone:  
post-1.0 
 Component:  django.contrib.admin   |   Version:  
1.0  
Resolution:  duplicate  |  Keywords:  
admin permissions
 Stage:  Unreviewed | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

  * status:  reopened => closed
  * resolution:  => duplicate

Comment:

 Please read the above discussion and ''do not'' reopen this ticket unless
 you can get a consensus on the dev list that this feature should be added.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7150: patch to implement view pemission in admin

[Django]

#7150: patch to implement view pemission in admin
+---
  Reporter:  Antonio Gallo   | Owner:  
nobody   
Status:  reopened   | Milestone:  
post-1.0 
 Component:  django.contrib.admin   |   Version:  
1.0  
Resolution: |  Keywords:  
admin permissions
 Stage:  Unreviewed | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by g...@ise.co.za):

  * status:  closed => reopened
  * version:  newforms-admin => 1.0
  * resolution:  duplicate =>
  * milestone:  => post-1.0

Comment:

 We have a very common situation where we have junior administrators that
 are only allowed to ADD news items and higher level admins that can
 CHANGE/DELETE them.

 Without a view permission it is not possible to do this, you have to give
 CHANGE rights to everybody (They must be able to see the list of news
 items to know what they have already added)

 Surely this functionality is within the scope of even the simplest admin
 application?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9880: Spaces in assignment of values of named parameters for 'url' template function raise 'TypeError'

[Django]

#9880: Spaces in assignment of values of named parameters for 'url' template
function raise 'TypeError'
--+-
  Reporter:  Art Skvira   | Owner:  
nobody
Status:  closed   | Milestone:  
  
 Component:  Uncategorized|   Version:  1.0 
  
Resolution:  invalid  |  Keywords:  
  
 Stage:  Unreviewed   | Has_patch:  0   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Comment (by Art Skvira ):

 But why formatting style has to be enforced in such way?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9880: Spaces in assignment of values of named parameters for 'url' template function raise 'TypeError'

[Django]

#9880: Spaces in assignment of values of named parameters for 'url' template
function raise 'TypeError'
--+-
  Reporter:  Art Skvira   | Owner:  
nobody
Status:  closed   | Milestone:  
  
 Component:  Uncategorized|   Version:  1.0 
  
Resolution:  invalid  |  Keywords:  
  
 Stage:  Unreviewed   | Has_patch:  0   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * status:  new => closed
  * resolution:  => invalid

Comment:

 Which is why the documentation shows you to do it without spaces.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9881: Auth login should pass current_site to template, not current_site.name

[Django]

#9881: Auth login should pass current_site to template, not current_site.name
-+--
  Reporter:  walterk | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by walterk):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9881: Auth login should pass current_site to template, not current_site.name

[Django]

#9881: Auth login should pass current_site to template, not current_site.name
+---
 Reporter:  walterk |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Authentication  | Version:  SVN   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Currently, django.contrib.auth's login method passes 'current_site.name'
 to the template:

 {{{
 return render_to_response(template_name, {
 'form': form,
 redirect_field_name: redirect_to,
 'site_name': current_site.name,
 }, context_instance=RequestContext(request))
 login = never_cache(login)
 }}}

 It would be preferable if the dictionary pair were site':
 current_site''' instead.  (This is how django-registration works.)  In my
 current project, 'site_name' overrides a variable defined in a custom
 context processor, which serves the same function.  We prefer to not use
 contrib.sites to pass the site name and domain to templates, since this
 requires slightly more set up and maintenance. (E.g., making sure
 'example.com' gets replaced whenever the database gets wiped.)

 Passing site': current_site''' instead of site_name':
 current_site.name''' would make contrib.auth behavior more consistent with
 the django-registration module as well.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9576: django.contrib.admin.widgets.AdminDateWidget.Media.js missing core.js

[Django]

#9576: django.contrib.admin.widgets.AdminDateWidget.Media.js missing core.js
---+
  Reporter:  eddymul   | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by AmanKow):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9880: Spaces in assignment of values of named parameters for 'url' template function raise 'TypeError'

[Django]

#9880: Spaces in assignment of values of named parameters for 'url' template
function raise 'TypeError'
---+
   Reporter:  Art Skvira   |Owner:  
nobody
 Status:  new  |Milestone:  
  
  Component:  Uncategorized|  Version:  1.0 
  
   Keywords:   |Stage:  
Unreviewed
  Has_patch:  0|   Needs_docs:  0   
  
Needs_tests:  0|   Needs_better_patch:  0   
  
---+
 When '=' sign in statement like this:

 {% url vj job_id=job.id %}

 is surrounded by spaces, ie.

 {% url vj job_id = job.id %}, view raises TypeError:

 http://dpaste.com/100225/

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9879: spam

[Django]

#9879: spam
+---
  Reporter: | Owner:  nobody  
Status:  closed | Milestone:  post-1.0
 Component:  Uncategorized  |   Version:  1.0 
Resolution:  invalid|  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * status:  new => closed
  * reporter:  anonymous =>
 * cc: cUNmirWS (removed)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * summary:  QBWcbNbCFTAAFOMzmX => spam
  * keywords:  tCDYsXJmyyopPjagrW =>
  * needs_docs:  => 0
  * resolution:  => invalid

Old description:

> n88kFa  http://bjpbkipohtde.com/";>bjpbkipohtde,
> [url=http://hlmuoxmdrcbp.com/]hlmuoxmdrcbp[/url],
> [link=http://mfjjsutzhjfh.com/]mfjjsutzhjfh[/link],
> http://dchufwuxrdiz.com/

New description:

 spam

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9879: QBWcbNbCFTAAFOMzmX

[Django]

#9879: QBWcbNbCFTAAFOMzmX
+---
 Reporter:  anonymous   |   Owner:  nobody
   Status:  new |   Milestone:  post-1.0  
Component:  Uncategorized   | Version:  1.0   
 Keywords:  tCDYsXJmyyopPjagrW  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 n88kFa  http://bjpbkipohtde.com/";>bjpbkipohtde,
 [url=http://hlmuoxmdrcbp.com/]hlmuoxmdrcbp[/url],
 [link=http://mfjjsutzhjfh.com/]mfjjsutzhjfh[/link],
 http://dchufwuxrdiz.com/

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9878: Database backend leaves idling connections when used in multiple threads

[Django]

#9878: Database backend leaves idling connections when used in multiple threads
---+
  Reporter:  Fredde| Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 The particular example you give is not the way Django is used, however.
 So, yes, if you do something to deliberately create lots of connections,
 lot of connections will be created. However, Django closes its connection
 to the database at the end of each request/response cycle, so there is
 only one connection in operation per thread or process handling requests
 and responses. If you're not using the HTTP layer, it's still only one
 connection per thread of execution and you are in complete control of the
 number of threads you create.

 So there's not really any Django bug here. The connection usage is
 predictable and controlled.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9874: Added template cache in template loader

[Django]

#9874: Added template cache in template loader
-+--
  Reporter:  novoya  | Owner:  novoya
Status:  reopened| Milestone:  post-1.0  
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:  template cache
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Comment (by mtredinnick):

 This is almost certainly going to cause rednering bugs. The Python objects
 representating templates are not just the compiled form, they also
 (intentionally) contain rendering state. It also assumes that the same
 name will load the same template in every thread, which isn't true (a
 dynamic template loader, for example). So there are larger considerations
 that don't seem to have been addressed here.

 Right now, this is probably the wrong approach to solving the perceived
 problem, but want to think about it some more.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9366: date and time filters do not use localized strings, missing datetime filter

[Django]

#9366: date and time filters do not use localized strings, missing datetime 
filter
---+
  Reporter:  bthomas   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by mtredinnick):

 You are simply saying that the second feature is necessary. Not that it is
 entirely and unrevocably part of the first bug fix. It will be quite
 possible to fix the first part without adding the second part. They are
 separable. This isn't a question of value.

 In any case, this is going around and around. The internationalisation fix
 will be done as part of a larger ticket. At that point, somebody can
 update this with a fix to add the missing bit.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #3254: [patch] experimental fulltext search support for postgres, oracle and mssql

[Django]

#3254: [patch] experimental fulltext search support for postgres, oracle and 
mssql
---+
  Reporter:  Ronny Pfannschmidt| Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

 * cc: tw...@twidi.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9878: Database backend leaves idling connections when used in multiple threads

[Django]

#9878: Database backend leaves idling connections when used in multiple threads
--+-
 Reporter:  Fredde|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 When creating and saving model instances in multiple threads, the database
 backend leaves idling connections. This will finally cause a "Too many
 connections"-exception.

 I'm using Django 1.0 with a MySQL database

 This script will leave ~10-20 open connections
 {{{
 def createArticle():
 a = Article(title = '...', text = '...')
 a.save()

 threads = []
 for i in xrange(200):
 t = threading.Thread(target = createArticle)
 t.start()
 threads.append(t)

 for t in threads:
 t.join()
 }}}

 To see the active connections in the mysql client
 {{{
 mysql> show full processlist;
 
++--+---+--+-+--+---+---+
 | Id | User | Host  | db   | Command | Time | State | Info
 |
 
++--+---+--+-+--+---+---+
 | 463987 |  | localhost | NULL | Query   |0 | NULL  | show full
 processlist |
 | 463994 |  | localhost |  | Sleep   |   44 |   | NULL
 |
 | 464020 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 | 464042 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 | 464045 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 | 464048 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 | 464067 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 | 464093 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 | 464105 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 | 464136 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 | 464139 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 | 464165 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 | 464166 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 | 464183 |  | localhost |  | Sleep   |   85 |   | NULL
 |
 
++--+---+--+-+--+---+---+
 14 rows in set (0.00 sec)
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9877: More Pythonic mutations of geometry objects

[Django]

#9877: More Pythonic mutations of geometry objects
---+
 Reporter:  Aryeh Leib Taurog   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  GIS| Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Experimenting with geodjango, I found myself immediately wanting easier,
 more Pythonic ways to manipulate the data in the GEOS geometry objects:

 {{{
 #!python
 geometryObj[i:j] = ((33.42,-70.89),(34.819,-67.61))
 }}}

 So I have extended the !LineString and !LinearRing classes'
 {{{__getitem__}}} and
 {{{__setitem__}}} methods to allow slicing, added a {{{__delitem__}}}
 while I was at it, and threw in most
 of the non-special, standard list methods as well.

 I'd like to do this for the geometry collections next, but I'm posting
 this here (is there a better place?) to solicit feedback on these mods
 before I continue.

 == Questions ==

 1. Is there some really good reason ''not'' to do this that I'm missing,
 or am
 I just the first one who wanted it enough to sit down and do it?

 2. Did I do this correctly?  It seems to work.  I tested the correctness
 of
 the mutations themselves, but haven't extensively tested the GEOS
 methods on the mutated objects.

 3. I've created a situation where

 {{{
 #!python
 del geometryObj[:]  # now works
 geometryObj = LinearString([]) # doesn't work
 }}}

 Is there some reason I shouldn't do that?

 4. Does it make sense to implement similar mutation methods for
 {{{Point}}}
 objects or {{{Polygon}}} objects?

 5. I think it would be nice to make the {{{LinearRing}}} mutations fool-
 proof.
 Meaning since the first and last point must be the same, a
 {{{LinearRing}}}
 object with ''n'' points should really behave like a list of ''n - 1''
 coordinates, all the while maintaining the last coordinate as a mirror of
 the first so that the geometry won't be invalidated by the mutations.
 Comments?

 6. I implemented {{{count()}}} which is redundant with {{{__len__()}}}
 and, in this
 case, {{{num_points()}}}.  Overkill?

 7. Also I'm not sure if {{{index(x)}}} and {{{remove(x)}}} made sense in
 this
 context, but I could imagine cases where they might be useful and so I
 erred on the side of implementing as much of the standard list interface
 as
 I thought reasonable.  Comments?

 8. The {{{sort()}}} and {{{reverse()}}} methods don't seem applicable
 here.  These are the
 only standard list methods which I did ''not'' implement.  However, I
 think
 that they might apply to the geometry collections.  Comments?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9873: Template reuse is worthless(when inheretiance or inclusion involved) because parent templates get re-compiled every time

[Django]

#9873: Template reuse is worthless(when inheretiance or inclusion involved)
because parent templates get re-compiled every time
--+-
  Reporter:  novoya   | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:  duplicate|  Keywords:  template cache
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by dc):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => duplicate
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Duplicate of #9874

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9874: Added template cache in template loader

[Django]

#9874: Added template cache in template loader
-+--
  Reporter:  novoya  | Owner:  novoya
Status:  reopened| Milestone:  post-1.0  
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:  template cache
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * stage:  Unreviewed => Design decision needed

Comment:

 It wasn't fixed. Somebody needs to learn how to read the documentation on
 the ticket process to find out what "fixed" means (hint: not "some random
 person uploaded a patch").

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9874: Added template cache in template loader

[Django]

#9874: Added template cache in template loader
--+-
  Reporter:  novoya   | Owner:  novoya
Status:  reopened | Milestone:  post-1.0  
 Component:  Template system  |   Version:  SVN   
Resolution:   |  Keywords:  template cache
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * status:  closed => reopened
  * resolution:  fixed =>

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9862: Non-standard SQL generated in column definition for nullable columns in create table DDL

[Django]

#9862: Non-standard SQL generated in column definition for nullable columns in
create table DDL
---+
  Reporter:  Ambrish   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ikelly):

  * has_patch:  0 => 1
  * component:  Uncategorized => Database layer (models, ORM)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9874: Added template cache in template loader

[Django]

#9874: Added template cache in template loader
--+-
  Reporter:  novoya   | Owner:  novoya
Status:  closed   | Milestone:  post-1.0  
 Component:  Template system  |   Version:  SVN   
Resolution:  fixed|  Keywords:  template cache
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Comment (by ElliottM):

 I'm confused, when was this fixed?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9876: Incorrect max_length specification

[Django]

#9876: Incorrect max_length specification
+---
  Reporter:  dberger| Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 You seem to be looking at the wrong docs.  The current version is here:

 http://docs.djangoproject.com/en/dev/intro/tutorial01/#id3

 and it does say max_length.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9875: urls.py instructions incomplete

[Django]

#9875: urls.py instructions incomplete
+---
  Reporter:  dberger| Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by brosner):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 It is clearly written as the third bullet point:
 http://docs.djangoproject.com/en/dev/intro/tutorial02/#activate-the-admin-
 site.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9876: Incorrect max_length specification

[Django]

#9876: Incorrect max_length specification
---+
 Reporter:  dberger|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 In tutorial 1, both development and v 0.96, the following code block is
 given.


 {{{
 from django.db import models

 class Poll(models.Model):
 question = models.CharField(maxlength=200)
 pub_date = models.DateTimeField('date published')

 class Choice(models.Model):
 poll = models.ForeignKey(Poll)
 choice = models.CharField(maxlength=200)
 votes = models.IntegerField()
 }}}

 I am using the latest non-development release, 1.0.2.  The necessary
 propert is max_length instead of maxlength.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9875: urls.py instructions incomplete

[Django]

#9875: urls.py instructions incomplete
---+
 Reporter:  dberger|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 This version of the tutorial does not instruct the user to uncomment the
 following lines in urls.py:

 from django.contrib import admin
 admin.autodiscover()

 It only instructs the user to uncomment:

 (r'^admin/(.*)', admin.site.root),


 Perhaps this is not necessary in v 0.96.  I am using v 1.0.2.  I was sent
 to this version of the tutorial because I am not using a development
 version.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9874: Added template cache in template loader

[Django]

#9874: Added template cache in template loader
--+-
  Reporter:  novoya   | Owner:  novoya
Status:  closed   | Milestone:  post-1.0  
 Component:  Template system  |   Version:  SVN   
Resolution:  fixed|  Keywords:  template cache
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Changes (by novoya):

  * status:  assigned => closed
  * summary:  Template reuse is worthless(when inheretiance or inclusion
  involved) because parent templates get re-
  compiled every time => Added template cache in
  template loader
  * resolution:  => fixed
  * needs_tests:  0 => 1
  * milestone:  => post-1.0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8571: comment framework throws obscure exception in {% comment_form_target %}

[Django]

#8571: comment framework throws obscure exception in {% comment_form_target %}
--+-
  Reporter:  sla...@gmail.com | Owner:  nobody  

Status:  closed   | Milestone:  post-1.0

 Component:  django.contrib.comments  |   Version:  1.0 

Resolution:  worksforme   |  Keywords:  comment, 
comment_form_target
 Stage:  Unreviewed   | Has_patch:  0   

Needs_docs:  0|   Needs_tests:  0   

Needs_better_patch:  0|  
--+-
Comment (by mandric):

 This is a bug in Django since the exception/stacktrace that gets rendered
 is nearly useless.  The problem is farther down in the stack and the
 templating plumbing is clogging up proper raising of the error.  Lately
 when I get TemplateSyntaxError it is unrelated to the actual problem I see
 this as an important issue for django.

 So after a thorough cleanup of my urls.py and removal of .pyc files this
 bug disappeared for me.  Sure it was a configuration issue but I had to
 guess where the problem might be so this is a bug in django since the
 proper exception was not raised.  It does not seem related to
 django.contrib.comments component but there should be a ticket open for
 this template plumbing issue.  It would be nice if we could link to that
 issue/ticket, if it exists, from this ticket.  A bit of testing to make
 sure the template system raises the correct error when there is an issue
 in urls.py would be a good start, not sure if that exists already.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9874: Template reuse is worthless(when inheretiance or inclusion involved) because parent templates get re-compiled every time

[Django]

#9874: Template reuse is worthless(when inheretiance or inclusion involved)
because parent templates get re-compiled every time
--+-
  Reporter:  novoya   | Owner:  novoya
Status:  assigned | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:   |  Keywords:  template cache
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by novoya):

  * owner:  nobody => novoya
  * needs_better_patch:  => 0
  * status:  new => assigned
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9874: Template reuse is worthless(when inheretiance or inclusion involved) because parent templates get re-compiled every time

[Django]

#9874: Template reuse is worthless(when inheretiance or inclusion involved)
because parent templates get re-compiled every time
-+--
 Reporter:  novoya   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Template system  | Version:  SVN   
 Keywords:  template cache   |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 The following view module fails to make good reuse to the template
 For each new request, all inherited/included templates will be recreated
 and compiled
 {{{
 tpl = loader.get_template('mytemplate.html')

 def view_func1(request):
  '''
 Any inherited templates from tpl
 will created and recompiled again and again
  '''
  return HttpResponse(tpl.render(context))
 }}}
 Attached a very simple patch to solve the problem:
 1.Simple template caching in the django.template.loader
 2.Minimum change in django.template.loader_tags

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9873: Template reuse is worthless(when inheretiance or inclusion involved) because parent templates get re-compiled every time

[Django]

#9873: Template reuse is worthless(when inheretiance or inclusion involved)
because parent templates get re-compiled every time
-+--
 Reporter:  novoya   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Template system  | Version:  SVN   
 Keywords:  template cache   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 The following view module fails to make good reuse to the template
 For each new request, all inherited/included templates will be recreated
 and compiled
 {{{
 tpl = loader.get_template('mytemplate.html')

 def view_func1(request):
  '''
 Any inherited templates from tpl
 will created and recompiled again and again
  '''
  return HttpResponse(tpl.render(context))
 }}}
 Attached a very simple patch to solve the problem:
 1.Simple template caching in the django.template.loader
 2.Minimum change in django.template.loader_tags

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9870: When querying aross a many to many field if the target is the primary key only join to the intermediary table

[Django]

#9870: When querying aross a many to many field if the target is the primary key
only join to the intermediary table
--+-
  Reporter:  Alex | Owner: 
Status:  closed   | Milestone: 
 Component:  ORM aggregation  |   Version:  1.0
Resolution:  fixed|  Keywords: 
 Stage:  Unreviewed   | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => fixed
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Fixed in github branch, commit ae196bf779c20c5559db4b637f95cfd1cdb8af3f.
 Thanks to Alex Gaynor for his help on this.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9366: date and time filters do not use localized strings, missing datetime filter

[Django]

#9366: date and time filters do not use localized strings, missing datetime 
filter
---+
  Reporter:  bthomas   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by Daniel Pope ):

 The second part is not independent. Imagine a culture that writes date as
 {{{dd/mm/}}} but date and time as {{{dd/mm hh:mm }}}. Whether any
 such culture exists I don't know, but an internationalisable datetime
 formatting system should be able to cope with this.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9872: error in example for sessions page

[Django]

#9872: error in example for sessions page
+---
  Reporter:  derek73| Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by derek73):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9872: error in example for sessions page

[Django]

#9872: error in example for sessions page
---+
 Reporter:  derek73|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 http://docs.djangoproject.com/en/dev/topics/http/sessions/#examples

 {{{
 def post_comment(request, new_comment):
 if request.session.get('has_commented', False):
 return HttpResponse("You've already commented.")
 c = comments.Comment(comment=new_comment)
 c.save()
 request.session['has_commented'] = True
 return HttpResponse('Thanks for your comment!')
 }}}

 should be

 {{{
 def post_comment(request, new_comment):
 if request.session.get('has_commented', True): #<-
 return HttpResponse("You've already commented.")
 c = comments.Comment(comment=new_comment)
 c.save()
 request.session['has_commented'] = True
 return HttpResponse('Thanks for your comment!')

 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9862: Non-standard SQL generated in column definition for nullable columns in create table DDL

[Django]

#9862: Non-standard SQL generated in column definition for nullable columns in
create table DDL
+---
  Reporter:  Ambrish| Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by gabor):

 * cc: ga...@nekomancer.net (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9862: Non-standard SQL generated in column definition for nullable columns in create table DDL

[Django]

#9862: Non-standard SQL generated in column definition for nullable columns in
create table DDL
+---
  Reporter:  Ambrish| Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by Ambrish):

 Hi,

 
 it's only NULL that is causing a problem on db2, right? NOT NULL is fine?
 [[BR]]
 

 With DB2, only NULL is causing a problem and with NOT NULL there are no
 issues.

 Regards,[[BR]]
 Ambrish Bhargava

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #373: Add support for multiple-column primary keys

[Django]

#373: Add support for multiple-column primary keys
---+
  Reporter:  jacob | Owner:  dcramer 
Status:  assigned  | Milestone:  post-1.0
 Component:  Database layer (models, ORM)  |   Version:  
Resolution:|  Keywords:  database
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by automatthias):

 * cc: automatthias (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---