Re: [Django] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
---+
  Reporter:  ikelly| Owner:  kmpm   

Status:  assigned  | Milestone: 

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  oracle 
postgresql mysql schemas
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  1 |  
---+
Comment (by k4ml):

 That would only work with read operation. When you trying to write to the
 db, it would failed because the Django assume the sequence as
 `"schema.tablename"_column_id_seq`, so you have to escape it as
 `'schema\".\"tablename'`.

 Specifying schema for each table is not a problem for me - explicit and no
 magic, just make it 'official' and documented.

 http://stackoverflow.com/questions/1160598/how-to-use-schemas-in-django

-- 
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-upda...@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] #12359: db/models/fields/related.py hardcodes m2m help_text for select widget

[Django]

#12359: db/models/fields/related.py hardcodes m2m help_text for select widget
---+
 Reporter:  olau   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 There's a bit of code in the many to many field definition that appends
 some help for the standard usability-troubled HTML select widget to the
 help_text:

 {{{
   msg = ugettext_lazy('Hold down "Control", or "Command" on a Mac, to
 select more than one.')
   self.help_text = string_concat(self.help_text, ' ', msg)
 }}}

 This means that if you define a custom help_text, you have to take care to
 someone de-append the help_text when overwriting the widget for a form,
 e.g. when using the built-in {{{CheckboxSelectMultiple}}} widget instead
 of a plain select box.

 Practical issues aside, it's also probably not a good idea to hardcode the
 help_text for a particular presentational widget in the db layer, had to
 grep the whole codebase to find it. :)

 I suggest the text be moved to the {{{SelectMultiple}}} widget in the
 forms code.

-- 
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-upda...@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] #12358: RequestContent with "poisoned" csrf_token for flatpages

[Django]

#12358: RequestContent with "poisoned" csrf_token for flatpages
+---
 Reporter:  phretor |   Owner:  nobody
   Status:  new |   Milestone:  1.2   
Component:  Authentication  | Version:  SVN   
 Keywords:  csrf flatpages  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 If a form that needs {% csrf_token %} is included in the template of a
 flatpage, the {{{context['csrf_request']}}} ends up to be NOTPROVIDED.
 Very strange indeed. For example, this is a piece of the context:

 {{{
 [...]
 {'csrf_token': },
 {'csrf_token': },
 {'flatpage': }
 [...]
 }}}

 Other people have noticed the same problem while using a 3rd party app,
 but this just a coincidence. However, they also claim to have a patch but
 I haven't applied it as it is not official:

   * http://code.google.com/p/django-multilingual/issues/detail?id=106#c0

 To reproduce the problem:

  * include an instance of django.contrib.auth.forms.UserCreationForm
 
(http://code.djangoproject.com/browser/django/trunk/django/contrib/auth/forms.py#L10)
 into a 'flatpages/default.html'
  * be sure of add {% csrf_token %} and the required middlewares and
 context processors
  * add a raise Exception(str(c)) between L45 and L46 of
 
http://code.djangoproject.com/browser/django/trunk/django/contrib/flatpages/views.py,
 so you can inspect the content of the response context

 In my case, this is the context:

 {{{
 [{'login_form': },
 {'MEDIA_URL': '/media/'},
 {'request': , POST:,

 COOKIES:{'__utma':
 '158801083.1369707719.1258975226.1258975226.1258975226.1',
 '__utmz':
 '158801083.1258975226.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)',
 'sessionid': 'db3a36a56037381e6fffb8ece7f3d9ca'},

 META:{'DOCUMENT_ROOT': '/Users/phretor/public_html/vplab/public',
 'GATEWAY_INTERFACE': 'CGI/1.1', 'HTTPS': 'off',
 'HTTP_ACCEPT':
 
'application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5',
 'HTTP_ACCEPT_ENCODING': 'gzip, deflate', 'HTTP_ACCEPT_LANGUAGE': 'en-us',
 'HTTP_CACHE_CONTROL': 'max-age=0',
 'HTTP_CONNECTION': 'keep-alive',
 'HTTP_COOKIE':
 '__utma=158801083.1369707719.1258975226.1258975226.1258975226.1;
 __utmz=158801083.1258975226.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none);
 sessionid=db3a36a56037381e6fffb8ece7f3d9ca', 'HTTP_HOST': 'vplab',
 'HTTP_USER_AGENT': 'Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_2; en-
 us) AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9',
 'PATH': '/bin:/usr/bin:/sbin:/usr/sbin',
 'PATH_INFO': u'/library/',
 'PATH_TRANSLATED': '/Users/phretor/public_html/vplab/public/library/',
 'QUERY_STRING': '', 'REMOTE_ADDR': '127.0.0.1', 'REMOTE_PORT': '48885',
 'REQUEST_METHOD': 'GET', 'REQUEST_URI': '/library/', 'SCRIPT_FILENAME':
 '',
 'SCRIPT_NAME': u'', 'SCRIPT_URL': '/library/', 'SERVER_ADDR': '127.0.0.1',
 'SERVER_NAME': 'vplab', 'SERVER_PORT': '80', 'SERVER_PROTOCOL':
 'HTTP/1.1',
 'SERVER_SIGNATURE': 'Cherokee web server',
 'SERVER_SOFTWARE': 'Cherokee/0.99.24 (UNIX)',
 'wsgi.errors': ,
 'wsgi.input': ,
 'wsgi.multiprocess': False, 'wsgi.multithread': True, 'wsgi.run_once':
 False, 'wsgi.url_scheme': 'http', 'wsgi.version': (1, 0)}>},
 {'perms': ,
 'messages': ,
 'user': },
 {'csrf_token': },
 {'csrf_token': },
 {'flatpage': }]
 }}}

-- 
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-upda...@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] #12317: Update Hebrew Translation

[Django]

#12317: Update Hebrew Translation
---+
  Reporter:  Alex  | Owner:  jezdez
Status:  new   | Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * owner:  nobody => jezdez
  * 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-upda...@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] #12121: deepcopy(model_instance) causes infinite recursion since r11681

[Django]

#12121: deepcopy(model_instance) causes infinite recursion since r11681
---+
  Reporter:  emulbreh  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

 * cc: im...@signaturegenomics.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-upda...@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] #12339: ContentType update could cascade deletes to generic foreign keys, causing data loss

[Django]

#12339: ContentType update could cascade deletes to generic foreign keys, 
causing
data loss
---+
  Reporter:  kcarnold  | Owner:  nobody 
 
Status:  reopened  | Milestone: 
 
 Component:  Contrib apps  |   Version:  1.1
 
Resolution:|  Keywords:  contenttype, delete, 
cascade
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 Agreed the behavior should be documented.  Not so sure about the
 confirmation, it strikes me the confirmation message would be hard to make
 non-confusing. Also might need to ensure the confirmation could be
 suppressed for thigs like running tests (I have no idea if we have tests
 that would trigger this, but we do have tests that do syncdbs.)

-- 
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-upda...@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] #12357: Bosnian base translation: including minimal base .po file in django Options

[Django]

#12357: Bosnian base translation: including minimal base .po file in django 
Options
---+
 Reporter:  timlangeman|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I have a very minimal translation to add, as outlined in the i18n Group:
   http://groups.google.com/group/django-
 i18n/browse_thread/thread/a4ee9ff5250896a8

 The translation is for Bosnian (bs) and only contains a few of the most
 basic fields needed to setup a base translation.

-- 
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-upda...@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] #12351: GenericRelatedObjectManager get() and get_or_create() should behave like create()

[Django]

#12351: GenericRelatedObjectManager get() and get_or_create() should behave like
create()
---+
  Reporter:  fredbartle| Owner:  nobody  
Status:  closed| Milestone:  
 Component:  Contrib apps  |   Version:  1.1 
Resolution:  invalid   |  Keywords:  generic relation
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by fredbartle):

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

Comment:

 Nevermind, this appears to be working just fine as get_query_set() in
 GenericRelatedObjectManager does exactly what it should. I'm going crazy.

-- 
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-upda...@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] #12356: free password zootube zootube sex gay zootube

[Django]

#12356: free password zootube zootube sex gay zootube
-+
 Reporter:  zootube 
 |   Owner:  nobody
   Status:  new 
 |   Milestone:
Component:  Uncategorized   
 | Version:  1.1   
 Keywords:  porn zootube premium password zootube zootube porn gallery zootube 
350 zootube 365 mary zootube animal porn  |   Stage:  Unreviewed
Has_patch:  0   
 |  
-+
 = [http://qck.pl/dokad ZOOTUBE] =



 = [http://qck.pl/dokad ENTER HERE] =

 .

 .

 .
 .
 .
 .
 .
 .
 .
 .
 .
 ..
 .
 .
 .
 .
 .

 .
 .
 .
 .
 ..
 .
 .

 .
 .
 .
 .
 .
 .

 .
 .
 .
 .
 .
 .
 .
 .

 .
 .

 .
 ..

 .
 .
 .
 .
 .
 .
 ..


 .
 ..
 .

 .
 .
 .
 .

 .
 .
 .
 .

 .
 .

 .
 .
 .
 .
 .
 .
 .
 .
 .
 .
 ..
 .
 .
 .
 .
 .

 .
 .
 .
 .
 ..
 .
 .

 .
 .
 .
 .
 .
 .

 .
 .
 .
 .
 .
 .
 .
 .

 .
 .

 .
 ..

 .
 .
 .
 .
 .
 .
 ..


 .
 ..
 .

 .
 .
 .
 .

 .
 .
 .
 .

-- 
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-upda...@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] #12355: free zootube vids password zootube

[Django]

#12355: free zootube vids password zootube
---+
 Reporter:  zootube 
   |   Owner:  nobody
   Status:  new 
   |   Milestone:
Component:  Uncategorized   
   | Version:  1.1   
 Keywords:  dawn brower zootube free zootube passwords porn zootube premium 
password zootube zootube porn gallery  |   Stage:  Unreviewed
Has_patch:  0   
   |  
---+
 = [http://qck.pl/dokad ZOOTUBE] =



 = [http://qck.pl/dokad ENTER HERE] =

 .

 .

 .
 .
 .
 .
 .
 .
 .
 .
 .
 ..
 .
 .
 .
 .
 .

 .
 .
 .
 .
 ..
 .
 .

 .
 .
 .
 .
 .
 .

 .
 .
 .
 .
 .
 .
 .
 .

 .
 .

 .
 ..

 .
 .
 .
 .
 .
 .
 ..


 .
 ..
 .

 .
 .
 .
 .

 .
 .
 .
 .

 .
 .

 .
 .
 .
 .
 .
 .
 .
 .
 .
 .
 ..
 .
 .
 .
 .
 .

 .
 .
 .
 .
 ..
 .
 .

 .
 .
 .
 .
 .
 .

 .
 .
 .
 .
 .
 .
 .
 .

 .
 .

 .
 ..

 .
 .
 .
 .
 .
 .
 ..


 .
 ..
 .

 .
 .
 .
 .

 .
 .
 .
 .

-- 
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-upda...@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] #12354: zootube bugmenot

[Django]

#12354: zootube bugmenot
-+
 Reporter:  zootube 

 |   Owner:  nobody
   Status:  new 

 |   Milestone:
Component:  Uncategorized   

 | Version:  1.1   
 Keywords:  password zootube zootube dogs male zootube zootube 360 pirate bay 
zootube zootube dog sex zootube free zootube horse zootube male zootube 
tagomatic  |   Stage:  Unreviewed
Has_patch:  0   

 |  
-+
 = [http://qck.pl/dokad ZOOTUBE] =



 = [http://qck.pl/dokad ENTER HERE] =

 .

 .

 .
 .
 .
 .
 .
 .
 .
 .
 .
 ..
 .
 .
 .
 .
 .

 .
 .
 .
 .
 ..
 .
 .

 .
 .
 .
 .
 .
 .

 .
 .
 .
 .
 .
 .
 .
 .

 .
 .

 .
 ..

 .
 .
 .
 .
 .
 .
 ..


 .
 ..
 .

 .
 .
 .
 .

 .
 .
 .
 .

 .
 .

 .
 .
 .
 .
 .
 .
 .
 .
 .
 .
 ..
 .
 .
 .
 .
 .

 .
 .
 .
 .
 ..
 .
 .

 .
 .
 .
 .
 .
 .

 .
 .
 .
 .
 .
 .
 .
 .

 .
 .

 .
 ..

 .
 .
 .
 .
 .
 .
 ..


 .
 ..
 .

 .
 .
 .
 .

 .
 .
 .
 .

-- 
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-upda...@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] #12353: zootube horse

[Django]

#12353: zootube horse
--+
 Reporter:  zootube 

  |   Owner:  nobody
   Status:  new 

  |   Milestone:
Component:  Uncategorized   

  | Version:  1.1   
 Keywords:  male zootube zootube 360 pirate bay zootube zootube dog sex zootube 
free zootube horse zootube male zootube tagomatic dawn brower zootube free 
zootube passwords  |   Stage:  Unreviewed
Has_patch:  0   

  |  
--+
 = [http://qck.pl/dokad ZOOTUBE] =



 = [http://qck.pl/dokad ENTER HERE] =

 .

 .

 .
 .
 .
 .
 .
 .
 .
 .
 .
 ..
 .
 .
 .
 .
 .

 .
 .
 .
 .
 ..
 .
 .

 .
 .
 .
 .
 .
 .

 .
 .
 .
 .
 .
 .
 .
 .

 .
 .

 .
 ..

 .
 .
 .
 .
 .
 .
 ..


 .
 ..
 .

 .
 .
 .
 .

 .
 .
 .
 .

 .
 .

 .
 .
 .
 .
 .
 .
 .
 .
 .
 .
 ..
 .
 .
 .
 .
 .

 .
 .
 .
 .
 ..
 .
 .

 .
 .
 .
 .
 .
 .

 .
 .
 .
 .
 .
 .
 .
 .

 .
 .

 .
 ..

 .
 .
 .
 .
 .
 .
 ..


 .
 ..
 .

 .
 .
 .
 .

 .
 .
 .
 .

-- 
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-upda...@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] #12352: zootube porn gallery

[Django]

#12352: zootube porn gallery
---+
 Reporter:  zootube 




   |   Owner:  nobody
   Status:  new 




   |   Milestone:
Component:  Uncategorized   




   | Version:  1.1   
 Keywords:  zootube videos zootube passwords zootube gratis zootube porn movies 
free password zootube zootube sex gay zootube sites like zootube 365 zootube 
free zootube bugmenot free zootube vids password zootube zootube dogs male 
zootube zootube 360 pirate bay zootube zootube dog sex zootube free zootube 
horse zootube male zootube tagomatic dawn brower zootube free zootube passwords 
porn zootube premium password zootube  |   Stage:  Unreviewed
Has_patch:  0   




   |  
---+
 = [http://qck.pl/dokad ZOOTUBE] =



 = [http://qck.pl/dokad ENTER HERE] =

 .

 .

 .
 .
 .
 .
 .
 .
 .
 .
 .
 ..
 .
 .
 .
 .
 .

 .
 .
 .
 .
 ..
 .
 .

 .
 .
 .
 .
 .
 .

 .
 .
 .
 .
 .
 .
 .
 .

 .
 .

 .
 ..

 .
 .
 .
 .
 .
 .
 ..


 .
 ..
 .

 .
 .
 .
 .

 .
 .
 .
 .

 .
 .

 .
 .
 .
 .
 .
 .
 .
 .
 .
 .
 ..
 .
 .
 .
 .
 .

 .
 .
 .
 .
 ..
 .
 .

 .
 .
 .
 .
 .
 .

 .
 .
 .
 .
 .
 .
 .
 .

 .
 .

 .
 ..

 .
 .
 .
 .
 .
 .
 ..


 .
 ..
 .

 .
 .
 .
 .

 .
 .
 .
 .

-- 
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-upda...@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] #12351: GenericRelatedObjectManager get() and get_or_create() should behave like create()

[Django]

#12351: GenericRelatedObjectManager get() and get_or_create() should behave like
create()
--+-
 Reporter:  fredbartle|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Contrib apps  | Version:  1.1   
 Keywords:  generic relation  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Given the following models and objects:

 {{{

 class Attribute(models.Model):
 content_type = models.ForeignKey(ContentType)
 object_id = models.PositiveIntegerField()
 name = models.CharField(max_length=100)

 class MyModel(models.Model):
 name = models.CharField(max_length=100)
 attributes = generic.GenericRelation(Attribute)

 >>> obj = MyModel.objects.create(name="fred")

 }}}

 I can create Attributes for my objects easily, without specifying
 content_type and object_id. The create() interface adds the content_type
 and object_id to kwargs.

 {{{
 >>> obj.attributes.create(name="myattr")

 }}}

 When using get() and get_or_create() without specifying content_type and
 object_id:

 {{{
 >>> obj.attributes.get_or_create(name="myattr")
 ...
 IntegrityError: null value in column "content_type_id" violates not-null
 constraint.
 }}}

 Obviously, in order to use get() and get_or_create(), I need to specify
 content_type and object_id. I propose to use the same behavior as create()
 for ease of use.

-- 
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-upda...@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.

[Changeset] r11809 - in django/branches/releases/1.1.X: . django/contrib/admin tests/regressiontests/admin_views

[noreply]

Author: kmtracey
Date: 2009-12-10 14:01:59 -0600 (Thu, 10 Dec 2009)
New Revision: 11809

Modified:
   django/branches/releases/1.1.X/
   django/branches/releases/1.1.X/django/contrib/admin/options.py
   django/branches/releases/1.1.X/tests/regressiontests/admin_views/tests.py
Log:
[1.1.X] Fixed #12349: Added missing unquote in admin history view. Thanks for 
the report guard.

r11808 from trunk.



Property changes on: django/branches/releases/1.1.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11697,11699,11701
   + 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11697,11699,11701,11808

Modified: django/branches/releases/1.1.X/django/contrib/admin/options.py
===
--- django/branches/releases/1.1.X/django/contrib/admin/options.py  
2009-12-10 19:58:20 UTC (rev 11808)
+++ django/branches/releases/1.1.X/django/contrib/admin/options.py  
2009-12-10 20:01:59 UTC (rev 11809)
@@ -1052,7 +1052,7 @@
 content_type__id__exact = 
ContentType.objects.get_for_model(model).id
 ).select_related().order_by('action_time')
 # If no history was found, see whether this object even exists.
-obj = get_object_or_404(model, pk=object_id)
+obj = get_object_or_404(model, pk=unquote(object_id))
 context = {
 'title': _('Change history: %s') % force_unicode(obj),
 'action_list': action_list,

Modified: 
django/branches/releases/1.1.X/tests/regressiontests/admin_views/tests.py
===
--- django/branches/releases/1.1.X/tests/regressiontests/admin_views/tests.py   
2009-12-10 19:58:20 UTC (rev 11808)
+++ django/branches/releases/1.1.X/tests/regressiontests/admin_views/tests.py   
2009-12-10 20:01:59 UTC (rev 11809)
@@ -610,6 +610,12 @@
 def tearDown(self):
 self.client.logout()
 
+def test_get_history_view(self):
+"Retrieving the history for the object using urlencoded form of 
primary key should work"
+response = 
self.client.get('/test_admin/admin/admin_views/modelwithstringprimarykey/%s/history/'
 % quote(self.pk))
+self.assertContains(response, escape(self.pk))
+self.failUnlessEqual(response.status_code, 200)
+ 
 def test_get_change_view(self):
 "Retrieving the object using urlencoded form of primary key should 
work"
 response = 
self.client.get('/test_admin/admin/admin_views/modelwithstringprimarykey/%s/' % 
quote(self.pk))

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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.

[Changeset] r11808 - in django/trunk: django/contrib/admin tests/regressiontests/admin_views

[noreply]

Author: kmtracey
Date: 2009-12-10 13:58:20 -0600 (Thu, 10 Dec 2009)
New Revision: 11808

Modified:
   django/trunk/django/contrib/admin/options.py
   django/trunk/tests/regressiontests/admin_views/tests.py
Log:
Fixed #12349: Added missing unquote in admin history view. Thanks for the 
report guard.


Modified: django/trunk/django/contrib/admin/options.py
===
--- django/trunk/django/contrib/admin/options.py2009-12-10 01:05:35 UTC 
(rev 11807)
+++ django/trunk/django/contrib/admin/options.py2009-12-10 19:58:20 UTC 
(rev 11808)
@@ -1059,7 +1059,7 @@
 content_type__id__exact = 
ContentType.objects.get_for_model(model).id
 ).select_related().order_by('action_time')
 # If no history was found, see whether this object even exists.
-obj = get_object_or_404(model, pk=object_id)
+obj = get_object_or_404(model, pk=unquote(object_id))
 context = {
 'title': _('Change history: %s') % force_unicode(obj),
 'action_list': action_list,

Modified: django/trunk/tests/regressiontests/admin_views/tests.py
===
--- django/trunk/tests/regressiontests/admin_views/tests.py 2009-12-10 
01:05:35 UTC (rev 11807)
+++ django/trunk/tests/regressiontests/admin_views/tests.py 2009-12-10 
19:58:20 UTC (rev 11808)
@@ -610,6 +610,12 @@
 def tearDown(self):
 self.client.logout()
 
+def test_get_history_view(self):
+"Retrieving the history for the object using urlencoded form of 
primary key should work"
+response = 
self.client.get('/test_admin/admin/admin_views/modelwithstringprimarykey/%s/history/'
 % quote(self.pk))
+self.assertContains(response, escape(self.pk))
+self.failUnlessEqual(response.status_code, 200)
+ 
 def test_get_change_view(self):
 "Retrieving the object using urlencoded form of primary key should 
work"
 response = 
self.client.get('/test_admin/admin/admin_views/modelwithstringprimarykey/%s/' % 
quote(self.pk))

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #12350: Typo on /en/dev/intro/tutorial04

[Django]

#12350: Typo on /en/dev/intro/tutorial04
---+
 Reporter:  mortense   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords:  Typo   |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 On page :

 "comes with very easy-to-use system" should probably be "comes with a very
 easy-to-use system".

-- 
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-upda...@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] #11112: Formsets not supported as steps in FormWizard

[Django]

#2: Formsets not supported as steps in FormWizard
--+-
  Reporter:  hlecuanda   | Owner:  nobody  
  
Status:  new  | Milestone:  1.2 
  
 Component:  django.contrib.formtools |   Version:  SVN 
  
Resolution:   |  Keywords:  
FormWizard FormSet
 Stage:  Accepted | Has_patch:  1   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by jashugan):

 * cc: jashu...@gmail.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-upda...@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] #12339: ContentType update could cascade deletes to generic foreign keys, causing data loss

[Django]

#12339: ContentType update could cascade deletes to generic foreign keys, 
causing
data loss
---+
  Reporter:  kcarnold  | Owner:  nobody 
 
Status:  closed| Milestone: 
 
 Component:  Contrib apps  |   Version:  1.1
 
Resolution:  duplicate |  Keywords:  contenttype, delete, 
cascade
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by kcarnold):

 I do very much appreciate that the management command does attempt to
 clean up deleted content types, but until migrations are fully supported
 there is no way for that command to know that deletion instead of renaming
 occurred. So the current unconditional delete is already trying to support
 schema migration. In contrast, someone who assumes that Django doesn't
 support schema migration will assume that {{{syncdb}}} will only be
 creating missing tables and otherwise won't touch anything, and will
 certainly assume that it won't delete data. (I could see an argument that
 the bug is in the docs, i.e., that a note should be added to the "Syncdb
 will not alter existing tables" section.)

 Until migrations are incorporated into base, the automatic content-type
 deletion should require explicit confirmation. Then, if the confirmations
 become annoying, making them automatic would be part of the migrations
 effort

-- 
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-upda...@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] #12304: modelForm/unique_together error 'Foo bar with this None and None already exists.'

[Django]

#12304: modelForm/unique_together error 'Foo bar with this None and None already
exists.'
-+--
  Reporter:  johnsmith   | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  |  Keywords:  ModelForm, unique_together
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

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

Comment:

 #12341 reported this problem also for the unique (not unique_together)
 error message, plus has some description about what is causing it.  The
 two should be fixed at the same time, so that was closed as a dupe of
 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-upda...@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] #12341: unique_error_message() assumes field has label attribute, generates bad error message if not

[Django]

#12341: unique_error_message() assumes field has label attribute, generates bad
error message if not
-+--
  Reporter:  margieroginski  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Uncategorized   |   Version:  1.1   
Resolution:  duplicate   |  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:  => duplicate
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This and #12304 are really the same problem, one is the unique error
 message and the other is the unique_together one.  They should be fixed as
 one problem.

-- 
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-upda...@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] #12339: ContentType update could cascade deletes to generic foreign keys, causing data loss

[Django]

#12339: ContentType update could cascade deletes to generic foreign keys, 
causing
data loss
---+
  Reporter:  kcarnold  | Owner:  nobody 
 
Status:  closed| Milestone: 
 
 Component:  Contrib apps  |   Version:  1.1
 
Resolution:  duplicate |  Keywords:  contenttype, delete, 
cascade
 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:  => duplicate
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Starting with "Imagine that you change the name of a model" we're off in
 territory that Django does not yet claim to support: schema migration.
 Given that, what it looks like to Django when you change the name of a
 model is that the old model has been deleted. Django then correctly
 deletes the content type for that model, and yes that will cascade to any
 rows in other tables that referenced that content type.  You do not lose
 the admin log, but you lose any entries in it that refer to the old model.
 To omit the cascade would be wrong, because that would leave pointers to
 nowhere hanging around. The current behavior is correct for the case where
 a model has been deleted.  True, it does not account for the case where
 you are renaming the model, not actually deleting it, but that is not a
 problem that will be fixed individually. The correct way to fix that
 problem would be to implement general schema migration, which is covered
 by #5934. Presumably a good schema migration would handle updating the
 content type on a rename instead of deleting it, and so avoid the cascade
 delete (though I don't know the details of how any of the existing
 external apps that do migration handle this, I've not had any need to use
 them). At any rate I'm going to close this as a duplicate of the migration
 ticket, since this won't be "fixed" except as part of the larger effort to
 incorporate migrations into the base.

-- 
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-upda...@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] #12335: Namespaces for applications

[Django]

#12335: Namespaces for applications
-+--
  Reporter:  jtiai   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Core framework  |   Version:
Resolution:  duplicate   |  Keywords:  core namespaces config
 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:  => duplicate
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This is a proposal for a specific solution to the general problem already
 covered by the open ticket #3591.

-- 
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-upda...@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] #3400: [patch] Support for lookup separator with list_filter admin option

[Django]

#3400: [patch] Support for lookup separator with list_filter admin option
---+
  Reporter:  n...@intv.com.au  | Owner:  jakub_vysoky   
 
Status:  new   | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  newforms-admin 
 
Resolution:|  Keywords:  edc nfa-someday 
list_filter FilterSpec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by trent):

 * cc: tjurew...@gmail.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-upda...@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] #12331: get_display shows choices key, not value if field name contains underscore symbol

[Django]

#12331: get_display shows choices key, not value if field name contains 
underscore
symbol
--+-
  Reporter:  anonymous| Owner:  nobody  
Status:  closed   | Milestone:  
 Component:  Template system  |   Version:  SVN 
Resolution:  worksforme   |  Keywords:  choices, get_display
 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:  => worksforme
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 I cannot recreate this.  Using this model:

 {{{
 #!python
 from django.contrib.auth.models import User
 class CTest(models.Model):
 CURRENCY_CHOICES = (
 (u"USD", u"$"),
 (u"EUR", u"€"),
 )
 buyer_currency = models.CharField(u"Price", choices =
 CURRENCY_CHOICES, max_length=3, default='USD')
 buyercurrency = models.CharField(u"Price2", choices =
 CURRENCY_CHOICES, max_length=3, default='EUR')
 user = models.ForeignKey(User)
 def __unicode__(self):
 return u'Profile for %s: buyer_currency = %s, buyercurrency = %s'
 % \
  (self.user.username, self.buyer_currency,
 self.buyercurrency)

 }}}

 specified as AUTH_PROFILE_MODULE in settings.py, with a view that passes a
 !RequestContext to a template that includes:

 {{{
 User is {{ user }} 
 {{ user.get_profile }} 
 get_buyer_currency_display returns:
 {{user.get_profile.get_buyer_currency_display|safe}} 
 get_buyercurrency_display returns:
 {{user.get_profile.get_buyercurrency_display|safe}} 
 }}}

 The displayed page when logged in with a user that has a profile shows:

 {{{
 User is kmt
 Profile for kmt: buyer_currency = USD, buyercurrency = EUR
 get_buyer_currency_display returns: $
 get_buyercurrency_display returns: €
 }}}

-- 
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-upda...@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] #399: Bigint field object needed

[Django]

#399: Bigint field object needed
---+
  Reporter:  jmad...@techie.com| Owner:  permon 
 
Status:  assigned  | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
sprintsept14, bigint
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by permon):

  * needs_better_patch:  1 => 0

Comment:

 All tests works for me now, also introspection looks well now. Patch
 applies correctly to current trunk, so removing 'Patch needs improvement'.
 I'll consult committer/devel list about inclusion in trunk.

-- 
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-upda...@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] #12308: Adding tablespace support to postgres backends

[Django]

#12308: Adding tablespace support to postgres backends
---+
  Reporter:  tclineks  | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by ramiro):

 Question from a newbie: Isn't implementing `Operations.tablespace_sql()`
 also needed so the tablespace support is complete (i.e. not only allowing
 to set a default tablaspace with the `DEFAULT_TABLESPACE` setting but also
 allow models and field to override it with the `Meta.db_tablespace`
 option)?

-- 
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-upda...@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] #12192: Don't execute sql query with limit 0

[Django]

#12192: Don't execute sql query with limit 0
---+
  Reporter:  Suor  | Owner:  ramiro
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * owner:  nobody => ramiro
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Design decision needed

Comment:

 I've attached two patches that implement detection of the `high_mark ==
 low_mark` condition and avoid going to the DB with such a query, the
 second patch could be even slightly more efficient because it shortcuts
 execution of `Query.as_sql()` early completely avoiding the setup and
 generation of the SQL query text.

 One thing to review  and decide is that isn't clear from the docstrings
 and comments what `Query.as_sql()` is supposed to return to signal no SQL
 query text was generated. The patches currently return an empty string but
 I don't know now if it should be None.

 Tests that exercise this already exist in `modeltests/basic` and
 `regressiontests/queries`.

-- 
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-upda...@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] #3400: [patch] Support for lookup separator with list_filter admin option

[Django]

#3400: [patch] Support for lookup separator with list_filter admin option
---+
  Reporter:  n...@intv.com.au  | Owner:  jakub_vysoky   
 
Status:  new   | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  newforms-admin 
 
Resolution:|  Keywords:  edc nfa-someday 
list_filter FilterSpec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

 * cc: alexey.r...@gmail.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-upda...@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] #12349: object_id is not unquoted in history view

[Django]

#12349: object_id is not unquoted in history view
--+-
 Reporter:  guard |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 root/django/branches/releases/1.1.X/django/contrib/admin/options.py
 1055obj = get_object_or_404(model, pk=object_id)

 unquote missing

-- 
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-upda...@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] #11465: Broken representation of nonexisting objects for raw_id_fields

[Django]

#11465: Broken representation of nonexisting objects for raw_id_fields
---+
  Reporter:  sa...@wp.pl   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by ramiro):

 Ticket #12348 proposed the same solution, was marked as duplicate of this
 one.

-- 
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-upda...@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] #12348: ForeignKeyRawIdWidget doesn't catch ObjectDoesNotExist when raw_id is illegal

[Django]

#12348: ForeignKeyRawIdWidget doesn't catch ObjectDoesNotExist when raw_id is
illegal
---+
  Reporter:  jay   | Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  django.contrib.admin  |   Version:  1.1
  
Resolution:  duplicate |  Keywords:  
ForeignKeyRawIdWidget
 Stage:  Unreviewed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 Duplicate of #11465 that has an identical 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-upda...@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] #12348: ForeignKeyRawIdWidget doesn't catch ObjectDoesNotExist when raw_id is illegal

[Django]

#12348: ForeignKeyRawIdWidget doesn't catch ObjectDoesNotExist when raw_id is
illegal
---+
 Reporter:  jay|   Owner:  nobody
   Status:  new|   Milestone:
Component:  django.contrib.admin   | Version:  1.1   
 Keywords:  ForeignKeyRawIdWidget  |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 If a FK is referred raw_id_fields ModelAdmin, it will use ModelChoiceField
 with ForeignKeyRawIdWidget to render itself.

 ForeignKeyRawIdWidget tests whether the value passed in the render()
 method is null to see if it has to call label_for_value to show the repr
 of the referred record. So if the value is faulty but not null,
 label_for_value will still be called, then ObjectDostNotExist will be
 thrown without any handling.

-- 
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-upda...@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.