Re: [Django] #10161: Fix F expressions with Oracle

[Django]

#10161: Fix F expressions with Oracle
---+
  Reporter:  ikelly| Owner:  ikelly
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Ian - I'm pretty sure this will fix the Oracle problems; if you can
 confirm that the expression tests pass with this patch, I'll commit it.

-- 
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
-~--~~~~--~~--~--~---

[Changeset] r9848 - in django/branches/releases/1.0.X: . django/test

[noreply]

Author: russellm
Date: 2009-02-21 01:29:21 -0600 (Sat, 21 Feb 2009)
New Revision: 9848

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/test/client.py
Log:
[1.0.X] Fixed #8551 -- Added REMOTE_ADDR to the default Test Client 
environment. Thanks to schmichael for the report and patch.

Merge of r9847 from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9810,9812,9821
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9810,9812,9821,9847

Modified: django/branches/releases/1.0.X/django/test/client.py
===
--- django/branches/releases/1.0.X/django/test/client.py2009-02-21 
07:19:12 UTC (rev 9847)
+++ django/branches/releases/1.0.X/django/test/client.py2009-02-21 
07:29:21 UTC (rev 9848)
@@ -189,6 +189,7 @@
 'HTTP_COOKIE':  self.cookies,
 'PATH_INFO': '/',
 'QUERY_STRING':  '',
+'REMOTE_ADDR':   '127.0.0.1',
 'REQUEST_METHOD':'GET',
 'SCRIPT_NAME':   '',
 'SERVER_NAME':   'testserver',


--~--~-~--~~~---~--~~
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] #1028: High-level feed framework should make more feed elements available

[Django]

#1028: High-level feed framework should make more feed elements available
+---
  Reporter:  ubernostrum| Owner:  ekarulf
Status:  assigned   | Milestone: 
 Component:  RSS framework  |   Version:  SVN
Resolution: |  Keywords:  feature_request
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by taojian):

 * cc: dan90 (removed)
 * cc: dan90., gir...@gmail.com (added)

Comment:

 Looks like this is stalled again.  I've got a basic patch for this mostly
 complete, adding these channel-level elements:

 managing_editor[[BR]]
 webmaster[[BR]]
 generator[[BR]]
 image[[BR]]
 stylesheet[[BR]]
 rating[[BR]]
 cloud[[BR]]
 skip_hours[[BR]]
 skip_days

 The others seemed esoteric or not useful. If anyone's got any half-
 complete patches lying around maybe we can consolidate them, otherwise
 I'll post a complete patch tomorrow.

-- 
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] #9268: Pass custom form values from post-comment to preview-comment

[Django]

#9268: Pass custom form values from post-comment to preview-comment
--+-
  Reporter:  taojian  | Owner:  stuartk
Status:  new  | Milestone:  post-1.0   
 Component:  django.contrib.comments  |   Version:  SVN
Resolution:   |  Keywords:  comment preview
 Stage:  Unreviewed   | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by taojian):

 I reported this originally, but since then I've started thinking that a
 far cleaner and more robust solution is just making your own custom
 CommentForm. That way custom values stick with postdata and get validated
 along with everything else. Right now, the only extraneous value that the
 post_comment view "listens" for is the "next" value: would it make sense
 to pass "next" along to the preview/errors form redisplay, and assume
 everything else is the responsibility of a custom form? It just seems so
 unwieldy to dump the whole POST dictionary back into the view.

 Just a thought...

-- 
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] #9268: Pass custom form values from post-comment to preview-comment

[Django]

#9268: Pass custom form values from post-comment to preview-comment
--+-
  Reporter:  taojian  | Owner:  stuartk
Status:  new  | Milestone:  post-1.0   
 Component:  django.contrib.comments  |   Version:  SVN
Resolution:   |  Keywords:  comment preview
 Stage:  Unreviewed   | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by kmtracey):

 Looks like the svn:eol-style native property is missing for that file
 (actually possibly the whole doc tree -- I can't find it set anywhere) so
 line ending differences caused the original diff to look like the whole
 file was changed.  I posted a diff using consistent line endings so just
 showing what actually new.

-- 
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] #4659: Save my hair! Add doc about "no module named "

[Django]

#4659: Save my hair! Add doc about "no module named "
+---
  Reporter:  anonymous  | Owner:  jacob
Status:  closed | Milestone:   
 Component:  Documentation  |   Version:  SVN  
Resolution:  wontfix|  Keywords:  python import
 Stage:  Unreviewed | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by floguy):

 I'm currently being hit by this same problem.  While I agree with Russ
 that Python is acting like it should, the real issue is that Django is
 swallowing up a traceback, and in doing so it is preventing me from seeing
 the real source of the 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-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] #10318: Template filter date format "U" produces a timestamp that is off by 10-14 days

[Django]

#10318: Template filter date format "U" produces a timestamp that is off by 
10-14
days
+---
  Reporter:  seanbrant  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
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:

 We've already got #9850 reporting the docs/code mismatch here.  We can use
 the one ticket for fixing the code, if the decision is to document this
 formatter and make it work properly.

-- 
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] #9850: Outdated documentation - (date format strings)

[Django]

#9850: Outdated documentation - (date format strings)
-+--
  Reporter:  cezz| Owner:  timo 
 
Status:  assigned| Milestone:   
 
 Component:  Documentation   |   Version:  SVN  
 
Resolution:  |  Keywords:  now format 
strings
 Stage:  Design decision needed  | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

  * stage:  Ready for checkin => Design decision needed

Comment:

 Before checking in a doc change that claims something works, we should
 first verify it works.  Adding a testcase that attempts to use this
 formatting option would seem to be wise.  Actually, based on #10318 and
 the associated django-users thread: http://groups.google.com/group/django-
 users/browse_thread/thread/5a156fbddee22d3b/e255ffea08bd3d4d, it appears
 the doc is more right than wrong here -- I can't see how the existing code
 is correct.

 I don't know whether the right answer is to to fix the code to match the
 doc (raise NotImplemented there, as it used to before r992) or fix the
 implementation.

 Note #10318 has a test, but that test fails on Windows due to
 strftime('%s') there returning an empty string rather then a number, so
 that test can't be directly used in our test suite.

-- 
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] #10318: Template filter date format "U" produces a timestamp that is off by 10-14 days

[Django]

#10318: Template filter date format "U" produces a timestamp that is off by 
10-14
days
---+
 Reporter:  seanbrant  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 When trying to format a date in a template with { mydate|date:"U"
 } the timestamp is off. Attached is a test case that first created a
 datetime object based on now then renders that in a template with the
 format {{{"U"}}} and compares that to outputting the date in python with
 {{{strftime('%s')}}}, this test fails. The next test outputs the date with
 the format {{{"Y-m-d H:i:s"}}} and compares that to outputting the date in
 python with {{{strftime(%F %T)}}}, this test passes. So it seems that only
 "U" is broken.

-- 
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] #10317: New Feature: django.contrib.markup.fields.MarkupField

[Django]

#10317: New Feature: django.contrib.markup.fields.MarkupField
---+
  Reporter:  jamesturk | Owner:  jamesturk   
Status:  new   | Milestone:  post-1.0
 Component:  Contrib apps  |   Version:  SVN 
Resolution:|  Keywords:  markup forms
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by jamesturk):

  * 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] #10317: New Feature: django.contrib.markup.fields.MarkupField

[Django]

#10317: New Feature: django.contrib.markup.fields.MarkupField
--+-
 Reporter:  jamesturk |   Owner:  jamesturk 
   Status:  new   |   Milestone:  post-1.0  
Component:  Contrib apps  | Version:  SVN   
 Keywords:  markup forms  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I recently published a snippet of something I've wanted in Django for a
 long time, a MarkupField that handles conversion to HTML on save and an
 accessor that calls mark_safe.

 My implementation is at http://www.djangosnippets.org/snippets/1332/
 (Credit where credit is due, I also borrowed the method of detecting which
 markup libraries are installed from a slightly less featured version
 http://www.djangosnippets.org/snippets/1169/)

 Jacob commented on Twitter that he'd like to see this as well and to
 submit a ticket.

 I'll put together the appropriate fields.py / documentation / tests and
 should have a candidate patch up soon.

-- 
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] #9268: Pass custom form values from post-comment to preview-comment

[Django]

#9268: Pass custom form values from post-comment to preview-comment
--+-
  Reporter:  taojian  | Owner:  stuartk
Status:  new  | Milestone:  post-1.0   
 Component:  django.contrib.comments  |   Version:  SVN
Resolution:   |  Keywords:  comment preview
 Stage:  Unreviewed   | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by stuartk):

 Diff for comments documentation added.

 Diff isn't that helpful, as it makes it unclear what has changed.  No
 changes to the original text, only an additional section right before the
 bottom notes section, detailing the use of the hidden 'next' tag.

-- 
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] #10316: `ping_google` missing from django_bash_completion script

[Django]

#10316: `ping_google` missing from django_bash_completion script
---+
 Reporter:  john_scott |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+


-- 
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] #10299: Enhance FileField form field with "delete" checkbox when file is loaded

[Django]

#10299: Enhance FileField form field with "delete" checkbox when file is loaded
-+--
  Reporter:  Valera_Grishin  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by Valera_Grishin):

 Replying to [comment:6 Valera_Grishin]:
 Is something wrong with Track? I only changed the cc, but didn't touch
 status and resolution. Why those changed too?

-- 
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] #10299: Enhance FileField form field with "delete" checkbox when file is loaded

[Django]

#10299: Enhance FileField form field with "delete" checkbox when file is loaded
-+--
  Reporter:  Valera_Grishin  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Valera_Grishin):

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

-- 
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] #10299: Enhance FileField form field with "delete" checkbox when file is loaded

[Django]

#10299: Enhance FileField form field with "delete" checkbox when file is loaded
-+--
  Reporter:  Valera_Grishin  | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Forms   |   Version:
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Valera_Grishin):

 * cc: valera.gris...@gmail.com (removed)
  * status:  closed => reopened
  * resolution:  duplicate =>

-- 
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] #7048: Support clearing FileFields with ModelForms

[Django]

#7048: Support clearing FileFields with ModelForms
---+
  Reporter:  jarrow| Owner:  brosner 
Status:  assigned  | Milestone:  post-1.0
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Changes (by Valera_Grishin):

 * cc: valera.gris...@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-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] #10315: objects.inv not available for intersphinx

[Django]

#10315: objects.inv not available for intersphinx
---+
 Reporter:  awatts |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I'm writing documentation for my Django app, and I'm using Sphinx with the
 [http://sphinx.pocoo.org/ext/intersphinx.html intersphinx] extension. I'd
 like to be able to cross-reference Django modules, but
 http://docs.djangoproject.com/en/dev/objects.inv either doesn't exist or
 is not served. Currently I'm making my own ad hoc inventory file, but it
 would be nice if I could reference the real one.

 See http://docs.python.org/objects.inv as an example of a site that does
 provide the cross-referencing information.

-- 
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] #7539: Add ON DELETE and ON UPDATE support to Django

[Django]

#7539: Add ON DELETE and ON UPDATE support to Django
---+
  Reporter:  glassfordm| Owner:  nobody  
Status:  new   | Milestone:  post-1.0
 Component:  Database layer (models, ORM)  |   Version:  SVN 
Resolution:|  Keywords:  feature 
 Stage:  Design decision needed| Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by ikelly):

 Is there a relevant difference between ON DELETE RESTRICT and the default?
 I ask because Oracle supports ON DELETE CASCADE and ON DELETE SET NULL but
 not ON DELETE RESTRICT.  For this reason, I think it would be preferable
 to omit the clause entirely rather than specify ON DELETE RESTRICT.

-- 
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] #10244: FileFields can't be set to NULL in the db

[Django]

#10244: FileFields can't be set to NULL in the db
+---
  Reporter:  oyvind | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Uncategorized  |   Version:  1.0 
Resolution: |  Keywords:  filefield NULL empty
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by oyvind):

 Example to test this issue:

 {{{
 #!python

 class File(models.Model):

 file = models.FileField(null=True, upload_to='files')
 }}}

 {{{
 #!python

 from models import File

 f = File()
 f.file = None
 f.save()

 from django.db import connection
 print connection.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-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] #10312: Wrong URL at "Outputting PDFs with Django" page

[Django]

#10312: Wrong URL at "Outputting PDFs with Django" page
+---
  Reporter:  JohnDoe| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * has_patch:  0 => 1
  * stage:  Unreviewed => Ready for checkin

-- 
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] #10262: Allow to clear object before deleting to avoid data loss because delete cascade behaviour

[Django]

#10262: Allow to clear object before deleting to avoid data loss because delete
cascade behaviour
---+
  Reporter:  msaelices | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by ikelly):

 This looks like a duplicate of #7539.

-- 
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] #10314: TestCase assert methods do not accept a msg parameter

[Django]

#10314: TestCase assert methods do not accept a msg parameter
---+
 Reporter:  wwinham|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Testing framework  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 django.test.TestCase assert methods, such as assertContains, do not accept
 a failure message as their final parameter, like the underlying unittest
 methods do.

-- 
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] #5791: Conditional get decorator

[Django]

#5791: Conditional get decorator
-+--
  Reporter:  man...@softwaremaniacs.org  | Owner:  nobody
Status:  new | Milestone:
 Component:  HTTP handling   |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by sfllaw):

 * cc: si...@akoha.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
-~--~~~~--~~--~--~---

Re: [Django] #10313: TypeError coercing to Unicode on DateTime Field

[Django]

#10313: TypeError coercing to Unicode on DateTime Field
+---
  Reporter:  pvickers   | 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 kmtracey):

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

Comment:

 You need to change your `__unicode__` method to:

 {{{
 #!python
 def __unicode__(self):
 return unicode(self.event_date)
 }}}

 [This is a Python requirement, nothing to do with Django.  `__unicode__`
 methods must return unicode (or, I guess, based on the message, string or
 buffer):

 {{{
 Python 2.5.1 (r251:54863, Jul 31 2008, 23:17:40)
 [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2
 Type "help", "copyright", "credits" or "license" for more information.
 >>> class Thing(object):
 ... def __init__(self, dt):
 ... self.dt = dt
 ... def __unicode__(self):
 ... return self.dt
 ...
 >>> import datetime
 >>> x = Thing(datetime.datetime.today())
 >>> unicode(x)
 Traceback (most recent call last):
   File "", line 1, in 
 TypeError: coercing to Unicode: need string or buffer, datetime.datetime
 found
 >>> unicode(x.dt)
 u'2009-02-20 11:39:35.925831'
 >>> class Thing2(object):
 ...def __init__(self, dt):
 ...   self.dt = dt
 ...def __unicode__(self):
 ...   return unicode(self.dt)
 ...
 >>> x = Thing2(datetime.datetime.today())
 >>> unicode(x)
 u'2009-02-20 11:40:54.093501'
 >>>

 }}}

 Returning x from a `__unicode__` method where unicode(x) would turn x into
 unicode isn't sufficient, Python requires that the `__unicode__` method do
 that explicitly.]

-- 
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] #7074: MySQL error/warning when 'gt' field lookup with a datetime field and fulltext search.

[Django]

#7074: MySQL error/warning when 'gt' field lookup with a datetime field and
fulltext search.
-+--
  Reporter:  anonymous   | Owner:   
  
Status:  new | Milestone:  post-1.0 
  
 Component:  Core framework  |   Version:  SVN  
  
Resolution:  |  Keywords:  qsrf-cleanup mysql, 
fulltext search, gt
 Stage:  Accepted| Has_patch:  0
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Comment (by reun):

 You can get around the bug by using .extra(). Instead of

 {{{task_set.filter(field__gt=time)}}}

 use

 {{{task_set.extra(where=['field > DATE(%s)'], params=[time])}}}.

-- 
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] #10313: TypeError coercing to Unicode on DateTime Field

[Django]

#10313: TypeError coercing to Unicode on DateTime Field
+---
  Reporter:  pvickers   | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by kmtracey):

 Replying to [comment:1 kmtracey]:
 > I really don't think you want to be using cx_oracle

 Oops, cat got involved in typing there, didn't mean to hit submit.  I was
 going to say I didn't think you want to be using cx_oracle 5.0, but
 perhaps 5.0.1 fixes the bug we'd had reported on that one earlier, so I'm
 not sure about that.  You might want to make sure 5.0.1 fixes the bug
 referenced here: http://code.djangoproject.com/ticket/9935#comment:4.
 (And all of this is an aside to the actual problem reported.)

-- 
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] #10310: Model attribute default_queryset

[Django]

#10310: Model attribute default_queryset
---+
  Reporter:  fero  | Owner:  nobody 
   
Status:  new   | Milestone:  post-1.0   
   
 Component:  Database layer (models, ORM)  |   Version:  1.0
   
Resolution:|  Keywords:  manager, 
queryset, enhancement
 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:

 The motivation for this is unclear to me.  Why would we want a 2nd way to
 do something that is already possible?  That just seems confusing.  What
 is the problem with defining a custom Manager that is solved by this
 approach?

-- 
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] #10313: TypeError coercing to Unicode on DateTime Field

[Django]

#10313: TypeError coercing to Unicode on DateTime Field
---+
 Reporter:  pvickers   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The error I'm getting is
 TypeError at /admin/dbasite/dbeventhistory/add/

 coercing to Unicode: need string or buffer, datetime.datetime found

 This occurs after doing a simple add using the automatically generated
 code by the Django admin interface.

 I'm running Django 1.0, using cx_Oracle to connect to an Oracle database.
 The cx_Oracle I have installed is version 5.0.1 but this exact same error
 also happens using version 4.4.
 I have reproduced this error using Oracle 9i and Oracle 10g.  On Oracle
 10g, I tested using Oracle characterset WE8ISO8859P1 and UTF8 - the error
 still occurs.

 I have a very simple model defined as:
 class DBEventHistory(models.Model):
 event_date = models.DateTimeField()
 description = models.CharField(max_length=1024)
 dba = models.ForeignKey(DBA)

 def __unicode__(self):
 return self.event_date

 class Meta:
 db_table = u'DB_EVENT_HISTORY'
 verbose_name_plural = ('DB Event History')

 The trace back I get is:
 Environment:

 Request Method: POST
 Request URL: http://cls049:8000/admin/dbasite/dbeventhistory/add/
 Django Version: 1.0-final-SVN-unknown
 Python Version: 2.4.3
 Installed Applications:
 ['django.contrib.auth',
  'django.contrib.admin',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.sites',
  'dbinfo.dbasite']
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware')


 Traceback:
 File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py" in
 get_response
   86. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/usr/lib/python2.4/site-packages/django/contrib/admin/sites.py" in
 root
   158. return self.model_page(request, *url.split('/', 2))
 File "/usr/lib/python2.4/site-packages/django/views/decorators/cache.py"
 in _wrapped_view_func
   44. response = view_func(request, *args, **kwargs)
 File "/usr/lib/python2.4/site-packages/django/contrib/admin/sites.py" in
 model_page
   177. return admin_obj(request, rest_of_url)
 File "/usr/lib/python2.4/site-packages/django/contrib/admin/options.py" in
 __call__
   191. return self.add_view(request)
 File "/usr/lib/python2.4/site-packages/django/db/transaction.py" in
 _commit_on_success
   238. res = func(*args, **kw)
 File "/usr/lib/python2.4/site-packages/django/contrib/admin/options.py" in
 add_view
   507. self.log_addition(request, new_object)
 File "/usr/lib/python2.4/site-packages/django/contrib/admin/options.py" in
 log_addition
   294. object_repr = force_unicode(object),
 File "/usr/lib/python2.4/site-packages/django/utils/encoding.py" in
 force_unicode
   49. s = unicode(s)

 Exception Type: TypeError at /admin/dbasite/dbeventhistory/add/
 Exception Value: coercing to Unicode: need string or buffer,
 datetime.datetime found

-- 
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] #10312: Wrong URL at "Outputting PDFs with Django" page

[Django]

#10312: Wrong URL at "Outputting PDFs with Django" page
+---
  Reporter:  JohnDoe| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by JohnDoe):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Documentation
  * 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] #10312: Wrong URL at "Outputting PDFs with Django" page

[Django]

#10312: Wrong URL at "Outputting PDFs with Django" page
---+
 Reporter:  JohnDoe|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The link to the user guide at [http://docs.djangoproject.com/en/dev/howto
 /outputting-pdf/ Outputting PDFs with Django] points to .com (and the
 wrong path), while it should be [http://www.reportlab.com/docs/reportlab-
 userguide.pdf This page].

-- 
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] #9806: GeometryField crashes contrib.gis.admin

[Django]

#9806: GeometryField crashes contrib.gis.admin
-+--
  Reporter:  ingenieroariel  | Owner:  jbronn   
Status:  assigned| Milestone:   
 Component:  GIS |   Version:  1.0  
Resolution:  |  Keywords:  admin, gis, GeometryField
 Stage:  Accepted| Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  1   |  
-+--
Comment (by johanneswilm):

 latest patch doesn't appy cleanly to 1.0.2 and even doing it by hand, the
 line:


 {{{
 else: self.params['collection_type'] =
 OGRGeomType(db_field._geom.replace('MULTI', ''))
 }}}

 creates problems, because "db_field" is not defined (it is in options.py,
 but not in widgets.py).

 I've checked the trunk-version, but couldn't find it there either.

-- 
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] #10311: Overriding the default manager at "import-time"

[Django]

#10311: Overriding the default manager at "import-time"
--+-
 Reporter:  fero  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:  manager   |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I tried to override the default manager
 when I am importing my views.

 I noticed that I needed to do override both;

  * objects attribute
  * _default_manager attribute

 In my views module I do something like

 {{{
 from app.models import MyModel
 from app.models.managers import MyManager

 MyModel.add_to_class('objects', MyManager())
 MyModel.add_to_class('_default_manager', MyManager())
 }}}

 Overriding the '_default_manager' attribute is needed in order to make
 the AnyModel.foreingKey_set working with the new custom manager.

 Is it correct and/or safe ?

-- 
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] #10310: Model attribute default_queryset

[Django]

#10310: Model attribute default_queryset
+---
 Reporter:  fero|   Owner:  nobody
   Status:  new |   Milestone:  post-1.0  
Component:  Database layer (models, ORM)| Version:  1.0   
 Keywords:  manager, queryset, enhancement  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 This enhancement aims to make the developer able to use its own
 specialized queryset
 without defining a custom Manager on the model. Custom manager
 is usually defined for:

  * custom filtering of default queryset
  * provide methods to perform custom operations on data

 I propose to provide Model with a "default_queryset" attribute
 to avoid defining the manager in the second case.

 The default manager get_query_set() must be modified in order to
 return self.model.default_queryset instance instead of
 QuerySet one.

 Furthermore default manager class must be modified like the following:

 {{{
 def __getattr__(self, attr):
   # Proxy to queryset
   try:
 rv = super(.).__getattr__(...)
   except AttributeError:
 rv = getattr(self.get_query_set(), attr)
   return rv
 }}}

 Example of usage:

 {{{
 class MyQuerySet(QuerySet):

def m1(self):
return self.filter(myfield=True)
def m2(self):
return self.exclude(myfield2__gte=10)

 class MyModel(models.Model):
default_queryset = MyQuerySet
 }}}

 If you are interested in this feature I can make 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] #7539: Add ON DELETE and ON UPDATE support to Django

[Django]

#7539: Add ON DELETE and ON UPDATE support to Django
---+
  Reporter:  glassfordm| Owner:  nobody  
Status:  new   | Milestone:  post-1.0
 Component:  Database layer (models, ORM)  |   Version:  SVN 
Resolution:|  Keywords:  feature 
 Stage:  Design decision needed| Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by miracle2k):

 * cc: miracle2k (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
-~--~~~~--~~--~--~---