Hi, I wonder if there is any recommendation or best practice on choosing
between
hybrid_property
and
hybrid_method
,
other than they hybrid_method can take arguments? If I use the
hybrid_method only throughout, without giving it a argument more than self,
doesn't it equal to using hybrid_prop
Hi *,
this post is a bit short on data because I just wrote a long posting and it
seems to have vanished when I hit the "POST" button. *sigh*
I am trying to do something (admittedly crazy) like this, but without the
after_flush hook - I'd rather like to tell the ORM that member_ids is
compute
Hello everybody,
I am currently pulling my hair out because I have a solution that I think
should work on the database side (albeit I don't like it), but I can't
figure out how to do this with sqlalchemy.
My current goal is to manage (long-lived) locks on copy-on-write
hierarchical data that is
On 08/23/2016 11:31 AM, Jinghui Niu wrote:
Thanks Mike. In future is it likely to have the instance level
expression and class level expression automatically translated by ORM?
It will be so much easier!
well a very small subset of them already are, but beyond that it's an
issue of increasin
Thanks Mike. In future is it likely to have the instance level expression
and class level expression automatically translated by ORM? It will be so
much easier!
On Mon, Aug 22, 2016 at 7:20 AM, Mike Bayer
wrote:
>
>
> On 08/22/2016 03:20 AM, Jinghui Niu wrote:
>
>> I'm creating a mixin for my ti
On 08/22/2016 02:50 PM, Rahul Ahuja wrote:
I'm having some trouble using Python string functions on VARCHAR columns
in MySQL (reflected using automap_base() and base.prepare). I'm getting
|
AttributeError:Neither'InstrumentedAttribute'objectnor
'Comparator'objectassociated withusers.middlename
if you have an Enum with a certain name that is to be used in multiple
tables, you can create it separately. Build the ENUM using the
create_type=False flag to keep it from generating the type
automatically, then use the .create() method to create it individually,
docs at
http://docs.sqlalch
On Monday, August 22, 2016 at 12:54:27 PM UTC+2, Simon King wrote:
>
>
> You'd probably be best off copying the SQLAlchemy code into your own
> project - it's not long:
>
>
> https://bitbucket.org/zzzeek/sqlalchemy/src/5145f671a4b5eb072e996bc450d2946d4be2a343/lib/sqlalchemy/ext/declarative/base.p