On Feb 25, 2014, at 2:17 AM, Luke wrote:
>
>
> Michael,
>
> I am continuing to get the same AmbiguousForeignKeysError with your first
> suggestion. Your simpler suggestion, using an abstract Base, does not seem to
> want to *easily* handle a many to many relationship in the base class.
> (
On Monday, February 24, 2014 1:12:59 PM UTC-8, Luke wrote:
>
>
>
> On Monday, February 24, 2014 12:55:16 PM UTC-8, Michael Bayer wrote:
>>
>>
>> On Feb 24, 2014, at 2:41 PM, Luke wrote:
>>
>> Hi,
>>
>>
>>
>> class Response(Writing):
>> # All responses are associated with Writing. Writing/Art
On Monday, February 24, 2014 12:55:16 PM UTC-8, Michael Bayer wrote:
>
>
> On Feb 24, 2014, at 2:41 PM, Luke > wrote:
>
> Hi,
>
>
>
> class Response(Writing):
> # All responses are associated with Writing. Writing/Articles may have
> # several responses
> #
> __tablename__ = 'res
On Feb 24, 2014, at 2:41 PM, Luke wrote:
> Hi,
>
>
>
> class Response(Writing):
> # All responses are associated with Writing. Writing/Articles may have
> # several responses
> #
> __tablename__ = 'response'
> id = Column('id', ForeignKey('writing.id'), primary_key=True)
Hi,
I'm looking for specific help with building an self-referential
relationship (adjacency?) inside of inherited ORM classes. I'm also looking
for a sanity check on the basic design of the classes since I'm not an
expert in SQL. This in the context of a Flask-sqlalchemy app resembling a
magaz
