Re: [Django] #14703: memcached.set_many() should not special case unicode data

2011-03-14 Thread Django
#14703: memcached.set_many() should not special case unicode data
+--
   Reporter:  gsakkis   |Owner:  nobody
 Status:  closed|Milestone:  1.3
  Component:  Cache system  |  Version:  1.2
 Resolution:  duplicate | Keywords:
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+--
Changes (by anonymous):

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


Comment:

 Closing this due to essentially duplication to #13686

 A pull request has been sent for this to be included in 1.3. I'll close
 that one when it's in.

-- 
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] #14703: memcached.set_many() should not special case unicode data

2010-12-03 Thread Django
#14703: memcached.set_many() should not special case unicode data
---+
  Reporter:  gsakkis   | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Cache system  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by accuser):

  * has_patch:  0 => 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-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] #14703: memcached.set_many() should not special case unicode data

2010-11-21 Thread Django
#14703: memcached.set_many() should not special case unicode data
---+
  Reporter:  gsakkis   | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Cache system  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 This is much like #13686. All get/set-type functions should be consistent
 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] #14703: memcached.set_many() should not special case unicode data

2010-11-16 Thread Django
#14703: memcached.set_many() should not special case unicode data
--+-
 Reporter:  gsakkis   |   Owner:  nobody
   Status:  new   |   Milestone:  1.3   
Component:  Cache system  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 memcached.set_many() tries to be "smart" by explicitly checking for
 unicode values and encoding them as utf-8; that's not even a default
 value, it is actually hardcoded.  The memcached.set() on the other hand
 just passes the value to the underlying memcached client. The bottom line
 is that the basic assumption that ''cache.set_many() is equivalent to
 calling cache.set() multiple times (but usually faster)'' is broken.

 FWIW I was bitten by this in real-world code, it's not a theoretical
 problem without actual use cases.

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