Both actually. I like the simplicity of just using the column_property as
is, but until the next release I will just use an explicit label and order
by that.
In case anyone else has this problem, my workaround was to add to the
column_property definition like so:
markerstatus = db.column_property(
db.select([MarkerStatus.status]).
where(MarkerStatus._marker_status_key==_marker_status_key).
label("markerstatus")
)
And in the order by I use the label like a string:
query.order_by("markerstatus")
Thanks!
On Monday, February 2, 2015 at 5:57:49 PM UTC-5, Michael Bayer wrote:
>
> the workaround, or using git master?
>
>
>
> Kevin S <kevin...@gmail.com <javascript:>> wrote:
>
> > Yes, that does fix the issue.
> >
> > --
> > 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+...@googlegroups.com <javascript:>.
> > To post to this group, send email to sqlal...@googlegroups.com
> <javascript:>.
> > Visit this group at http://groups.google.com/group/sqlalchemy.
> > For more options, visit https://groups.google.com/d/optout.
>
--
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.
