Re: [Sqlalchemy-tickets] [sqlalchemy] #2187: Consider Introducing new generic, unsigned numeric data types

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

#2187: Consider Introducing new generic, unsigned numeric data types
-------------------------+--------------------------------------------------
 Reporter:  guest        |          Owner:  zzzeek              
     Type:  enhancement  |         Status:  new                 
 Priority:  medium       |      Milestone:  0.7.2               
Component:  engine       |       Severity:  minor - half an hour
 Keywords:  unsigned     |   Status_field:  not decided upon    
-------------------------+--------------------------------------------------
Changes (by zzzeek):

  * status_field:  awaiting triage => not decided upon


Comment:

 Why favor "unsigned" and not zerofill/display_width accepted by MySQL
 numerics, collation accepted by MySQL and MSSQL string types,
 timezone/precision accepted by PG time/timestamp types, etc.   Any given
 project that wants to use one of those modifiers on certain platforms,
 among many others, would have the same problem.


 A generalized solution would be preferable:

 {{{
 #!python

 Column("mycolumn", type_switch(Integer, mysql.INTEGER(unsigned=True))
 }}}

 the above is pretty easy to build with a TypeDecorator (the dialect could
 be determined based on module identity).   If a solid syntax were devised
 it would be an easy feature add too.

 another idea, build it into `TypeEngine`:

 {{{
 #!python

 Column("mycolumn", Integer().with_variant(mysql.INTEGER(unsigned=True)))
 }}}


 with approaches like the above the problem of db-agnostic apps with db-
 specific type construction is solved in the general case.

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