While there may be legitimate reasons to choose the numeric type instead of the money type. This might not always be an option for people, especially when working with existing database. If a type is supported by a database back end there is no reason why it couldn't and shouldn't be supported by SQLAlchemy, especially when features like TypeDecorators and compiler extensions make doing so easy.
On Dec 27, 1:01 pm, Julien Cigar <jci...@ulb.ac.be> wrote: > don't use the MONEY type in PostgreSQL, use NUMERIC instead. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
