Re: [Sqlalchemy-tickets] [sqlalchemy] #2252: Use VARCHAR2 rather than VARCHAR on Oracle

[sqlalchemy <mi...@zz...>]

#2252: Use VARCHAR2 rather than VARCHAR on Oracle
---------------------------------+------------------------------------------
    Reporter:  guest             |       Owner:  zzzeek                 
        Type:  defect            |      Status:  closed                 
    Priority:  medium            |   Milestone:  0.7.3                  
   Component:  oracle            |    Severity:  minor - half an hour   
  Resolution:  fixed             |    Keywords:  Oracle VARCHAR VARCHAR2
Status_field:  completed/closed  |  
---------------------------------+------------------------------------------
Changes (by zzzeek):

  * status:  new => closed
  * resolution:  => fixed
  * status_field:  in progress => completed/closed


Comment:

 we'll use VARCHAR2 for String, as well as a new type VARCHAR2.  If someone
 explicitly puts VARCHAR i still think we should stick to the
 "uppercase=WYSIWYG" policy - Oracle is never going to change VARCHAR IMHO
 - but if they did, then VARCHAR should be generating the string VARCHAR in
 any case since it actually means something.

 r63a5f60b661b

-- 
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2252#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python