Re: [Django] #9282: Inclusion of comment-utils moderator facility

[Django]

#9282: Inclusion of comment-utils moderator facility
--+-
  Reporter:  thejaswi_puthraya| Owner:  nobody  

Status:  new  | Milestone:  

 Component:  django.contrib.comments  |   Version:  SVN 

Resolution:   |  Keywords:  spam filter, 
comments, comment-utils
 Stage:  Design decision needed   | Has_patch:  1   

Needs_docs:  0|   Needs_tests:  0   

Needs_better_patch:  0|  
--+-
Changes (by thejaswi_puthraya):

  * needs_docs:  1 => 0

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

Re: [Django] #10066: can per-site cache and per-view cache or some low level cache work together?

[Django]

#10066: can per-site cache and per-view cache or some low level cache work
together?
+---
  Reporter:  ubestim| Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mtredinnick):

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

Comment:

 Please ask questions like this on the django-users mailing list or in the
 #django IRC channel. This Trac install is only for bug reports. Thanks.

-- 
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] #10066: can per-site cache and per-view cache or some low level cache work together?

[Django]

#10066: can per-site cache and per-view cache or some low level cache work
together?
---+
 Reporter:  ubestim|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 can per-site cache and per-view cache or some low level cache work
 together?
 my purpose is to cache the whole site for anonymous and cache serveral
 view for registered user only.

 first, i set these in per-site cache in settings.py:
 CACHE_BACKEND = 'memcached://100.13.192.7:11211/'
 CACHE_MIDDLEWARE_SECONDS = 600
 CACHE_MIDDLEWARE_ANONYMOUS_ONLY = True

 this means only cache for anonymous.

 then i set some per-view cache as below:
 @cache_page(60 * 15)
 def slashdot_this(request):

 so view of slashdot_this will cache for register user and anonymous.

 am i right?

 If I have added the middleware needed for per-site cache,the cache
 middleware will cache again the data already cached
 by my view?
 Can you give more explanation in cache settings for using one of per-
 persite and per-view/low level and  using them together?

-- 
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] #10065: url patterns exception message missing space

[Django]

#10065: url patterns exception message missing space
+---
  Reporter:  Matthew Flanagan   | 
Owner:  nobody
Status:  new| 
Milestone:
 Component:  Core framework |   
Version:  1.0   
Resolution: |  
Keywords:
 Stage:  Unreviewed | 
Has_patch:  1 
Needs_docs:  0  |   
Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Matthew Flanagan ):

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

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

[Django] #10065: url patterns exception message missing space

[Django]

#10065: url patterns exception message missing space
---+
 Reporter:  Matthew Flanagan   |   Owner:  nobody   
 
   Status:  new|   Milestone:   
 
Component:  Core framework | Version:  1.0  
 
 Keywords: |   Stage:  
Unreviewed
Has_patch:  0  |  
---+
 A string that has been broken across multiple lines is missing a space at
 the end of the first line.

-- 
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] #10064: error: annotate doesn't support select_related

[Django]

#10064: error: annotate doesn't support select_related
--+-
  Reporter:  olivius  | Owner:  
Status:  new  | Milestone:  post-1.0
 Component:  ORM aggregation  |   Version:  SVN 
Resolution:   |  Keywords:  annotate
 Stage:  Unreviewed   | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Old description:

> models.py:[[BR]]
> {{{
> class Account(models.Model):
> accountname = models.CharField(max_length=20)
> account_creator = models.ForeignKey(User)
> description = models.TextField(_('description'), blank=True)
>
> def __unicode__(self):
> return self.account
>

> class Category(models.Model):
> category_name = models.CharField(max_length=50)
> category_creator = models.ForeignKey(User)
> description = models.TextField(_('description'), blank=True)
> def __unicode__(self):
> return self.category
>

> class Transaction(models.Model):
> category= models.ForeignKey(Category)
> account_from= models.ForeignKey(Account,
> related_name='account_from')
> account_to  = models.ForeignKey(Account,
> related_name='account_to')
> creator = models.ForeignKey(User)
> label   = models.CharField(_('label'), max_length=30)
> description = models.TextField(_('description'), blank=True)
> ammount = models.DecimalField(_('amount'),max_digits=8,
> decimal_places=2)
> created_at  = models.DateTimeField(_('created at'),
> default=datetime.now)
> updated_at  = models.DateTimeField(_('updated at'))
>
> def __unicode__(self):
> return self.label
> }}}
>
> shell:[[BR]]
>
> '''transactions=Transaction.objects.select_related('category','account_from','account_to').annotate(Sum('amount')).order_by('category','updated_at')'''
>
> '''print transactions'''
> {{{
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
> 239, in __getitem__
> return list(qs)[0]
>   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
> 163, in __len__
> self._result_cache.extend(list(self._iter))
>   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
> 294, in iterator
> setattr(obj, aggregate, row[i+aggregate_start])
> IndexError: tuple index out of range
> }}}

New description:

 models.py:[[BR]]
 {{{
 class Account(models.Model):
 accountname = models.CharField(max_length=20)
 account_creator = models.ForeignKey(User)
 description = models.TextField(_('description'), blank=True)

 def __unicode__(self):
 return self.account


 class Category(models.Model):
 category_name = models.CharField(max_length=50)
 category_creator = models.ForeignKey(User)
 description = models.TextField(_('description'), blank=True)
 def __unicode__(self):
 return self.category


 class Transaction(models.Model):
 category= models.ForeignKey(Category)
 account_from= models.ForeignKey(Account,
 related_name='account_from')
 account_to  = models.ForeignKey(Account,
 related_name='account_to')
 creator = models.ForeignKey(User)
 label   = models.CharField(_('label'), max_length=30)
 description = models.TextField(_('description'), blank=True)
 ammount = models.DecimalField(_('amount'),max_digits=8,
 decimal_places=2)
 created_at  = models.DateTimeField(_('created at'),
 default=datetime.now)
 updated_at  = models.DateTimeField(_('updated at'))

 def __unicode__(self):
 return self.label
 }}}

 shell:[[BR]]

 {{{
 >>>
 
transactions=Transaction.objects.select_related('category','account_from','account_to').annotate(Sum('amount')).order_by('category','updated_at')
 >>> print transactions
 Traceback (most recent call last):
   File "", line 1, in 
   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
 239, in __getitem__
 return list(qs)[0]
   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
 163, in __len__
 self._result_cache.extend(list(self._iter))
   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
 294, in iterator
 setattr(obj, aggregate, row[i+aggregate_start])
 IndexError: tuple index out of range
 }}}

Comment (by Alex):

 cleaned up the formatting of the description slightly.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

Re: [Django] #10064: error: annotate doesn't support select_related

[Django]

#10064: error: annotate doesn't support select_related
--+-
  Reporter:  olivius  | Owner:  
Status:  new  | Milestone:  post-1.0
 Component:  ORM aggregation  |   Version:  SVN 
Resolution:   |  Keywords:  annotate
 Stage:  Unreviewed   | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

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

Re: [Django] #10060: Multiple table annotation failure

[Django]

#10060: Multiple table annotation failure
--+-
  Reporter:  svsha...@intellecap.net  | Owner:  
Status:  new  | Milestone:  post-1.0
 Component:  ORM aggregation  |   Version:  SVN 
Resolution:   |  Keywords:  
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

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

Re: [Django] #10064: error: annotate doesn't support select_related

[Django]

#10064: error: annotate doesn't support select_related
--+-
  Reporter:  olivius  | Owner:  
Status:  new  | Milestone:  post-1.0
 Component:  ORM aggregation  |   Version:  SVN 
Resolution:   |  Keywords:  annotate
 Stage:  Unreviewed   | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Old description:

> {{{
> models.py:[[BR]]
>
> class Account(models.Model):
> accountname = models.CharField(max_length=20)
> account_creator = models.ForeignKey(User)
> description = models.TextField(_('description'), blank=True)
>
> def __unicode__(self):
> return self.account
>

> class Category(models.Model):
> category_name = models.CharField(max_length=50)
> category_creator = models.ForeignKey(User)
> description = models.TextField(_('description'), blank=True)
> def __unicode__(self):
> return self.category
>

> class Transaction(models.Model):
> category= models.ForeignKey(Category)
> account_from= models.ForeignKey(Account,
> related_name='account_from')
> account_to  = models.ForeignKey(Account,
> related_name='account_to')
> creator = models.ForeignKey(User)
> label   = models.CharField(_('label'), max_length=30)
> description = models.TextField(_('description'), blank=True)
> ammount = models.DecimalField(_('amount'),max_digits=8,
> decimal_places=2)
> created_at  = models.DateTimeField(_('created at'),
> default=datetime.now)
> updated_at  = models.DateTimeField(_('updated at'))
>
> def __unicode__(self):
> return self.label
> }}}
>
> shell:[[BR]]
>
> '''transactions=Transaction.objects.select_related('category','account_from','account_to').annotate(Sum('amount')).order_by('category','updated_at')'''
>
> '''print transactions'''
>
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
> 239, in _
> _getitem__
> return list(qs)[0]
>   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
> 163, in _
> _len__
> self._result_cache.extend(list(self._iter))
>   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
> 294, in i
> terator
> setattr(obj, aggregate, row[i+aggregate_start])
> IndexError: tuple index out of range

New description:

 models.py:[[BR]]
 {{{
 class Account(models.Model):
 accountname = models.CharField(max_length=20)
 account_creator = models.ForeignKey(User)
 description = models.TextField(_('description'), blank=True)

 def __unicode__(self):
 return self.account


 class Category(models.Model):
 category_name = models.CharField(max_length=50)
 category_creator = models.ForeignKey(User)
 description = models.TextField(_('description'), blank=True)
 def __unicode__(self):
 return self.category


 class Transaction(models.Model):
 category= models.ForeignKey(Category)
 account_from= models.ForeignKey(Account,
 related_name='account_from')
 account_to  = models.ForeignKey(Account,
 related_name='account_to')
 creator = models.ForeignKey(User)
 label   = models.CharField(_('label'), max_length=30)
 description = models.TextField(_('description'), blank=True)
 ammount = models.DecimalField(_('amount'),max_digits=8,
 decimal_places=2)
 created_at  = models.DateTimeField(_('created at'),
 default=datetime.now)
 updated_at  = models.DateTimeField(_('updated at'))

 def __unicode__(self):
 return self.label
 }}}

 shell:[[BR]]

 
'''transactions=Transaction.objects.select_related('category','account_from','account_to').annotate(Sum('amount')).order_by('category','updated_at')'''

 '''print transactions'''
 {{{
 Traceback (most recent call last):
   File "", line 1, in 
   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
 239, in __getitem__
 return list(qs)[0]
   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
 163, in __len__
 self._result_cache.extend(list(self._iter))
   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
 294, in iterator
 setattr(obj, aggregate, row[i+aggregate_start])
 IndexError: tuple index out of range
 }}}

Comment (by kmtracey):

 (Fixed formatting.)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You 

Re: [Django] #10064: error: annotate doesn't support select_related

[Django]

#10064: error: annotate doesn't support select_related
--+-
  Reporter:  olivius  | Owner:  
Status:  new  | Milestone:  post-1.0
 Component:  ORM aggregation  |   Version:  SVN 
Resolution:   |  Keywords:  annotate
 Stage:  Unreviewed   | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by olivius ):

  * 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] #10064: error: annotate doesn't support select_related

[Django]

#10064: error: annotate doesn't support select_related
+---
 Reporter:  olivius |  Status:  new
Milestone:  post-1.0|   Component:  ORM aggregation
  Version:  SVN |Keywords:  annotate   
Stage:  Unreviewed  |   Has_patch:  0  
+---
 {{{
 models.py:[[BR]]

 class Account(models.Model):
 accountname = models.CharField(max_length=20)
 account_creator = models.ForeignKey(User)
 description = models.TextField(_('description'), blank=True)

 def __unicode__(self):
 return self.account


 class Category(models.Model):
 category_name = models.CharField(max_length=50)
 category_creator = models.ForeignKey(User)
 description = models.TextField(_('description'), blank=True)
 def __unicode__(self):
 return self.category


 class Transaction(models.Model):
 category= models.ForeignKey(Category)
 account_from= models.ForeignKey(Account,
 related_name='account_from')
 account_to  = models.ForeignKey(Account,
 related_name='account_to')
 creator = models.ForeignKey(User)
 label   = models.CharField(_('label'), max_length=30)
 description = models.TextField(_('description'), blank=True)
 ammount = models.DecimalField(_('amount'),max_digits=8,
 decimal_places=2)
 created_at  = models.DateTimeField(_('created at'),
 default=datetime.now)
 updated_at  = models.DateTimeField(_('updated at'))

 def __unicode__(self):
 return self.label
 }}}

 shell:[[BR]]

 
'''transactions=Transaction.objects.select_related('category','account_from','account_to').annotate(Sum('amount')).order_by('category','updated_at')'''

 '''print transactions'''

 Traceback (most recent call last):
   File "", line 1, in 
   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
 239, in _
 _getitem__
 return list(qs)[0]
   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
 163, in _
 _len__
 self._result_cache.extend(list(self._iter))
   File "C:\Python25\lib\site-packages\django\db\models\query.py", line
 294, in i
 terator
 setattr(obj, aggregate, row[i+aggregate_start])
 IndexError: tuple index out of range

-- 
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] #10063: postgres dbshell asks for password even though I have .pgpass

[Django]

#10063: postgres dbshell asks for password even though I have .pgpass
---+
  Reporter:  walter+dja...@wjd.nu  | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  django-admin.py   |   Version:  SVN
   
Resolution:|  Keywords:  dbshell postgres 
psql password
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by carljm):

 * cc: c...@dirtcircle.com (added)
  * 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
-~--~~~~--~~--~--~---

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

[Django]

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

> I didn't like it was missing.
>
> oracle, mssql : add a FulltextIndex for the Fields
>
> postgresql: for each FulltextField add a extra tsvector Field named like
> "%(fieldname)_tsv"
>
> Problems with sqlite fts:
> * they stated a match statement may only be used once in a query
> * it needs a very specific syntax to search multiple fields
> * i have no idea how to get that into the ORM

New description:

 I didn't like it was missing.

 oracle, mssql : add a !FulltextIndex for the Fields

 postgresql: for each !FulltextField add a extra tsvector Field named like
 `"%(fieldname)_tsv"`

 Problems with sqlite fts:

  * they stated a match statement may only be used once in a query
  * it needs a very specific syntax to search multiple fields
  * i have no idea how to get that into the ORM

Comment (by ramiro):

 (description)

-- 
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] r9773 - django/trunk/tests/regressiontests/serializers_regress

[noreply]

Author: kmtracey
Date: 2009-01-18 14:54:42 -0600 (Sun, 18 Jan 2009)
New Revision: 9773

Modified:
   django/trunk/tests/regressiontests/serializers_regress/tests.py
Log:
Corrected code in serializers_regress testcase so that, in the case where an 
exception has been raised, rollback is called before attempting to leave 
transaction management.  With the old code the original exception 
(IntegrityError on InnoDB) was getting hidden by a transaction management error 
resulting from attempting to leave transaction management with a pending 
commit/rollback. 


Modified: django/trunk/tests/regressiontests/serializers_regress/tests.py
===
--- django/trunk/tests/regressiontests/serializers_regress/tests.py 
2009-01-17 23:06:23 UTC (rev 9772)
+++ django/trunk/tests/regressiontests/serializers_regress/tests.py 
2009-01-18 20:54:42 UTC (rev 9773)
@@ -360,8 +360,11 @@
 objects.extend(func[0](pk, klass, datum))
 instance_count[klass] = 0
 transaction.commit()
-finally:
+except:
+transaction.rollback()
 transaction.leave_transaction_management()
+raise
+transaction.leave_transaction_management()
 
 # Get a count of the number of objects created for each class
 for klass in instance_count:
@@ -381,8 +384,11 @@
 for obj in serializers.deserialize(format, serialized_data):
 obj.save()
 transaction.commit()
-finally:
+except:
+transaction.rollback()
 transaction.leave_transaction_management()
+raise
+transaction.leave_transaction_management()
 
 # Assert that the deserialized data is the same
 # as the original source


--~--~-~--~~~---~--~~
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] #9315: Keyword arguments with spaces and the url tag

[Django]

#9315: Keyword arguments with spaces and the url tag
--+-
  Reporter:  alexisbellido| Owner:  nobody  
Status:  new  | Milestone:  
 Component:  Template system  |   Version:  1.0 
Resolution:   |  Keywords:  url, tplrf-fixed
 Stage:  Unreviewed   | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by airrob):

 * cc: airrob (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] #7732: Oracle Backend with SessionPool

[Django]

#7732: Oracle Backend with SessionPool
---+
  Reporter:  halturin  | Owner:  nobody 
  
Status:  new   | Milestone:  post-1.0   
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords:  
yandex-sprint oracle session pool
 Stage:  Design decision needed| Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by mboersma):

  * keywords:  yandex-sprint => yandex-sprint oracle session pool

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

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

[Django]

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

  * keywords:  => oracle fulltext search

-- 
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] #9275: ORA-01830 date format picture ends before converting entire input... admin

[Django]

#9275: ORA-01830 date format picture ends before converting entire input... 
admin
---+
  Reporter:  hollerith | Owner:  nobody 

Status:  new   | Milestone: 

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

Resolution:|  Keywords:  oracle 
date formats
 Stage:  Unreviewed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by mboersma):

 * cc: ikelly, mboersma (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] #6148: Add generic support for database schemas

[Django]

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

Status:  new   | 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 |  
---+
Changes (by mboersma):

 * cc: mboersma (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] #9794: GeoDjango Distance Test Failures on Oracle 11g

[Django]

#9794: GeoDjango Distance Test Failures on Oracle 11g
-+--
  Reporter:  jbronn  | Owner:  jbronn 
Status:  new | Milestone: 
 Component:  GIS |   Version:  1.0
Resolution:  |  Keywords:  gis oracle 11g distance
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by mboersma):

 * cc: ikelly, mboersma (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] #7732: Oracle Backend with SessionPool

[Django]

#7732: Oracle Backend with SessionPool
---+
  Reporter:  halturin  | Owner:  nobody 
  
Status:  new   | Milestone:  post-1.0   
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords:  
yandex-sprint
 Stage:  Design decision needed| Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by mboersma):

 * cc: mboersma (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] #4186: [boulder-oracle] Error using "SELECT DISTINCT" with TextFields

[Django]

#4186: [boulder-oracle] Error using "SELECT DISTINCT" with TextFields
---+
  Reporter:  khoo...@westnet.com.au| Owner:  nobody 

Status:  new   | Milestone: 

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

Resolution:|  Keywords:  oracle 
distinct NCLOB TextField
 Stage:  Accepted  | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by mboersma):

 * cc: mboersma (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] #4140: [boulder-oracle]: manage.py syncdb fails with ORA-06552 when a fieldname is a keyword

[Django]

#4140: [boulder-oracle]: manage.py syncdb fails with ORA-06552 when a fieldname 
is
a keyword
-+--
  Reporter:  frank.hoffsum...@gmail.com  | Owner:  ikelly   
Status:  assigned| Milestone:   
 Component:  django-admin.py |   Version:  SVN  
Resolution:  |  Keywords:  oracle Oracle
 Stage:  Accepted| Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by mboersma):

 * cc: mboersma (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] #3254: [patch] experimental fulltext search support for postgres, oracle and mssql

[Django]

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

 * cc: mboersma (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] #8630: Improve the comments framework customizability

[Django]

#8630: Improve the comments framework customizability
--+-
  Reporter:  thejaswi_puthraya| Owner:  carljm  
   
Status:  new  | Milestone:  
   
 Component:  django.contrib.comments  |   Version:  SVN 
   
Resolution:   |  Keywords:  comments, 
customization
 Stage:  Accepted | Has_patch:  1   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by thejaswi_puthraya):

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

Comment:

 The latest patch is based on carljm's patch with a few changes. Docs are
 courtesy of carljm. Thanks carljm.

-- 
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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  Alex
Status:  assigned  | Milestone:  
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * owner:  nobody => Alex
  * status:  new => assigned

Comment:

 The issue is with the way root_path is handled, this may require some of
 the reversing stuff malcolm and I discussed on the mailing list.

-- 
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] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  1.0
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Ready for checkin | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Comment (by anonymous):

 There is an error, this line in admin_list.py:
   result_name = repr(escape(force_unicode(result_id).replace("'",
 '')))[1:]
 Should be:
   result_name = repr(escape(force_unicode(result).replace("'",
 '')))[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] #10060: Multiple table annotation failure

[Django]

#10060: Multiple table annotation failure
--+-
  Reporter:  svsha...@intellecap.net  | Owner:  
Status:  new  | Milestone:  post-1.0
 Component:  ORM aggregation  |   Version:  SVN 
Resolution:   |  Keywords:  
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Old description:

> Annotating across multiple tables results in wrong answers. i.e.
>
> In [110]: total =
> Branch.objects.all().annotate(total=Sum('center__client__loan__amount'))
>
> In [111]: total[0].total
> Out[111]: 3433000
>
> In [112]: repaid =
> Branch.objects.all().annotate(repaid=Sum('center__client__loan__payment_schedule__payments__principal'))
>
> In [113]: repaid[0].repaid
> Out[113]: 1976320.0
>
> In [114]: both =
> Branch.objects.all().annotate(total=Sum('center__client__loan__amount'),repaid=Sum('center__client__loan__payment_schedule__payments__principal'))
>
> In [115]: both[0].repaid
> Out[115]: 1976320.0
>
> In [116]: both[0].total
> Out[116]: 98816000
>   ^^^
>
> Compare the output of total in 116 vs. 111 (the correct answer).

New description:

 Annotating across multiple tables results in wrong answers. i.e.

 {{{
 In [110]: total =
 Branch.objects.all().annotate(total=Sum('center__client__loan__amount'))

 In [111]: total[0].total
 Out[111]: 3433000

 In [112]: repaid =
 
Branch.objects.all().annotate(repaid=Sum('center__client__loan__payment_schedule__payments__principal'))

 In [113]: repaid[0].repaid
 Out[113]: 1976320.0

 In [114]: both =
 
Branch.objects.all().annotate(total=Sum('center__client__loan__amount'),repaid=Sum('center__client__loan__payment_schedule__payments__principal'))

 In [115]: both[0].repaid
 Out[115]: 1976320.0

 In [116]: both[0].total
 Out[116]: 98816000
   ^^^
 }}}

 Compare the output of total in 116 vs. 111 (the correct answer).

Comment (by ubernostrum):

 (formatting)

-- 
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] #10062: inspectdb could use random field to inspect table

[Django]

#10062: inspectdb could use random field to inspect table
+---
  Reporter:  phoebebright   | Owner:  nobody
Status:  closed | Milestone:
 Component:  django-admin.py inspectdb  |   Version:  1.0   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mtredinnick):

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

Comment:

 That wouldn't solve any problem, since, by the same logic, the random
 record could contain bad data as well. It's just as likely. You're right
 about this being a problem with the database (since it let the bad data in
 there in the first place). This isn't a problem Django should even attempt
 to solve.

-- 
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] #10062: inspectdb could use random field to inspect table

[Django]

#10062: inspectdb could use random field to inspect table
---+
 Reporter:  phoebebright   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  django-admin.py inspectdb  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Currently uses the first record SELECT * FROM %s LIMIT 1
 If there is bad data in the first record it can fail
 eg. Warning: Incorrect datetime value: '11437866' for function str_to_time
 I know this is really a problem with the database and could potentially be
 confusing and slow - but how about picking a random record.

 SELECT * FROM %s ORDER BY RAND() LIMIT 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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

  * stage:  Unreviewed => Accepted

Comment:

 Confirmed. Only happens when one uses the {{{include(admin.site.urls)}}}
 form, so it's something introduced around r9739.

-- 
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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by lashni):

  * needs_better_patch:  => 0
  * component:  Uncategorized => django.contrib.admin
  * 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] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
 Reporter:  lashni |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I'm using revision 9772 and the development server. After starting a new
 project, activating the admin interface and logging in.. admin displays an
 incorrect logout link.

 http://127.0.0.1:8000/admin/admin/logout/

 Logs out successfully if I remove the duplicate admin.

-- 
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] #10060: Multiple table annotation failure

[Django]

#10060: Multiple table annotation failure
--+-
  Reporter:  svsha...@intellecap.net  | Owner:  
Status:  new  | Milestone:  post-1.0
 Component:  ORM aggregation  |   Version:  SVN 
Resolution:   |  Keywords:  
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Comment (by svsha...@intellecap.net):

 if you unzip agg_test.tar.gz, start a django shell in the project and run
 count.py in the shell, you will see the error being reproduced.

 cheers
 Sid

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