so youre looking to use the data-conversion properties of a type ? Well to do this right now, you can create another Table object where you explicitly name out all the columns with whatever datatypes you want, and then create a mapper to that. Although thats a little hackish, since both tables will have the same name one is going to replace the other.
It might be a better idea to expand the ColumnProperty object, which is the "column inside of a mapper" object, to support a type object that overrides that of the Column object its representing. Or maybe, just the ability to pass it a function for "preprocessing" and "postprocessing". Which would you prefer ? I'll look into this (the ColumnProperty class is right near the top of mapping/properties.py). Andreas Kostyrka wrote: > Hi! > > Is there any way to make a mapper create columns with a given type > instead of using the database supplied one? (And I know I could always > add a property get/set for the column but that makes for ugly > application level code :(, IMHO). > > Andreas > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Sqlalchemy-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
