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_
the workaround, or using git master?
Kevin S 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+uns
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+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalch
Kevin S wrote:
>
> This particular summary is ordering model objects by a column_property.
> Because of how our schema is setup, we use these column_properties often to
> eager load a single column from a one-to-one relationship (or petal table).
> The error is that sometimes it does the or
I apologize up front for not being able to provide a reproducible example
of my problem.
We have built a web app in sqlalchemy for read-only access of our
production database. We are in the process of migrating from one database
architecture (Sybase) to another (Postgres). The goal is to have t
