Sorry I didn't look closely. Yes when you subclass FKC overriding
_set_parent() to perform additional steps is one way to establish on-connect
details. Another is to use event.listen(ImplicitForeignKeyConstraint,
"after_parent_attach"), it would be a little more of the public API.
On Aug 6,
So IFKC(ImplicitForeignKeyConstraint) should not have inherited FKC? I did it
so that it could seamlessly be passed into Table() and __table_args__.
PS: Everyone, the repo is at https://bitbucket.org/fayaz/implicit
On Friday, August 05, 2011 07:31:44 PM Michael Bayer wrote:
> yeah wow I just saw
yeah wow I just saw that.Can you use table.add_constraint(fk) instead of
_set_parent() ?
On Aug 5, 2011, at 1:34 AM, Fayaz Yusuf Khan wrote:
> So I had been working on this tiny project now and then. And here's the poc.
> http://paste.pound-python.org/show/10578/
> I think I'm somewhat m
So I had been working on this tiny project now and then. And here's the poc.
http://paste.pound-python.org/show/10578/
I think I'm somewhat misusing the _set_parent() here though.
On Sunday, July 24, 2011 06:52:45 PM Michael Bayer wrote:
> On Jul 24, 2011, at 8:39 AM, Fayaz Yusuf Khan wrote:
> > T
On Jul 24, 2011, at 8:39 AM, Fayaz Yusuf Khan wrote:
>
> The problem with using different mixins is that you lose out on a lot of code
> reusability. In my case, I have a 'user' column that appears in almost all
> table declarations. To have a separate mixin class for each joint-table
> inher
On Saturday 23 Jul 2011 8:24:31 PM Michael Bayer wrote:
> On Jul 23, 2011, at 7:54 AM, Fayaz Yusuf Khan wrote:
> >> When C inherits from CMixin and Timeline, Python's method resolution is
> >> going to put TMixin after Timeline, that is:
> >>
> >> (, , >> '__main__.Timeline'>, , >> 'sqlalchemy.e
