Re: [Django] #11898: oracle quote_name bug

2010-02-03 Thread Django
#11898: oracle quote_name bug
---+
  Reporter:  steveed   | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:  wontfix   |  Keywords:  oracle, 
quote_name
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Please don't reopen tickets marked wontfix; take it up on django-
 developers.

 If you do, please be sure to explain why this wouldn't be backwards-
 incompatible.

-- 
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] #11898: oracle quote_name bug

2010-01-05 Thread Django
#11898: oracle quote_name bug
---+
  Reporter:  steveed   | Owner:  nobody 
   
Status:  reopened  | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:|  Keywords:  oracle, 
quote_name
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by steveed):

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

Comment:

 I am not sure why it is a won't fix. As is it doesn't work with how oracle
 tables are named. Oracle tables can be upper case or mixed case, and
 currently django states the sql requirement and then ignores it. I think
 this is a bug it should not return name upper unless the name is not
 quoted.

-- 
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] #11898: oracle quote_name bug

2009-12-18 Thread Django
#11898: oracle quote_name bug
---+
  Reporter:  steveed   | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:  wontfix   |  Keywords:  oracle, 
quote_name
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by ikelly):

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

Comment:

 This would be a very backward-incompatible change, breaking any model or
 field that has lowercase letters in its name.  I don't see it happening
 without a very compelling reason.

-- 
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] #11898: oracle quote_name bug

2009-12-18 Thread Django
#11898: oracle quote_name bug
---+
  Reporter:  steveed   | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.1
   
Resolution:|  Keywords:  oracle, 
quote_name
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by ikelly):

 * cc: ikelly, mboersma (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-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] #11898: oracle quote_name bug

2009-09-17 Thread Django
#11898: oracle quote_name bug
--+-
 Reporter:  steveed   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1   
 Keywords:  oracle, quote_name|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 In the below snippet of code from db/backends/oracle/base.py it appears
 that regardless of the how the name is sent in it is returned in
 uppercase. If believe line 155 should be 'return name'

 Thanks,
 Stephen

 {{{

 147def quote_name(self, name):
 148# SQL92 requires delimited (quoted) names to be case-sensitive.
 When
 149# not quoted, Oracle has case-insensitive behavior for
 identifiers, but
 150# always defaults to uppercase.
 151# We simplify things by making Oracle identifiers always
 uppercase.
 152if not name.startswith('"') and not name.endswith('"'):
 153name = '"%s"' % util.truncate_name(name.upper(),
 154   self.max_name_length())
 155return name.upper()

 }}}

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