Thanks Simon !
I got it working using the hack.
I'm not using the "mapper_configured" event because I need to add a
"parent" attribute to the subclass of TreeNode,
which should be done before the mapping.
On Friday, February 17, 2017 at 6:21:57 PM UTC+8, Simon King wrote:
>
> On Fri, Feb 17,
I am using Python 3.3 with sqlalchemy using a MySql 5.6.33 Database with
SQLAlchemy 1.1.5. I know that mysql supports Geo data types, but I was
unable to find the equivalent in sqlalchemy in the docs. I did see
GeoAlchemy and GeoAlchemy2 but GeoAlchemy is not for Python 3 and I am not
using a
you want "Node.connected" to be the set of all nodes connected in either
direction.The problem is that relationally, all graphs are
"directed", so we have the "left", "right" aspect of things.
The easiest way to get ".connected" as the union of both sets (hint!) is
to just union them in
I apologize if this is well trodden ground, but having googled, and
stack-overflowed, read the docs, and searched this list, where lots of
people have asked the same (or similar) questions, I couldn't find a
concrete answer...
I'm trying to set up a Model such that an entry can be connected
On 02/21/2017 03:56 PM, Shane Carey wrote:
I understand from the docs and several questions both here and on
bitbucket that cascading polymorphism is not supported. This
is what it says on the docs:
Warning
Currently, *only one discriminator column may be set*, typically on the
base-most
I understand from the docs and several questions both here and on bitbucket
that cascading polymorphism is not supported. This
is what it says on the docs:
Warning
Currently, *only one discriminator column may be set*, typically on the
base-most class in the hierarchy. “Cascading” polymorphic
