Hi Jonathan,
Yes, but as I mentioned in the original post, this is to improve an
existing system and a solution that does not involve changes to the
database schema would be ideal.
I think I've found a way forward by adding a column with column_property
and then using a synonym to with a descriptor to get / set the data. This
removes some of the odd code I had.
On Friday, September 18, 2015 at 7:30:37 PM UTC+2, Jonathan Vanasco wrote:
>
> If I understand you correctly, I would just do this:
>
> 1. Use 3 different columns for the value -- each a native data type.
> 2. Use `coalesce` to handle sorting
> 3. When displaying in sqlalchemy, just use a property to proxy displaying
> the set column (and explicitly work with the correct columns otherwise)
>
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
