Hi Mike,
On Tue, 27 Jul 2010 09:07:15 -0400, Michael Bayer
wrote:
> On Jul 27, 2010, at 1:34 AM, Faheem Mitha wrote:
>> My usage is slightly non-standard - a foreign key pointing to a
>> foreign key.
> that never worked, most likely. its very complicated to get the
> types to propagate up a
On Jul 27, 2010, at 1:34 AM, Faheem Mitha wrote:
> My
> usage is slightly non-standard - a foreign key pointing to a foreign
> key.
that never worked, most likely. its very complicated to get the types to
propagate up a chain like that, and all on a deferred execution, in a
reasonable way.
>
[This message has also been posted.]
Hi Lance,
Thanks for the quick reply.
On Mon, 26 Jul 2010 17:09:06 -0500, Lance Edgar wrote:
> I had a similar question a little while back and here was the answer:
http://groups.google.com/group/sqlalchemy/browse_thread/thread/1e861e9d1a0fefde
(url on one
Update:
On Tue, 27 Jul 2010, Faheem Mitha wrote:
Hi,
It turns out my example was too hasty. I should have had something like
foobar = Table(
'foo', meta,
Column('id', Integer, nullable=False, primary_key=True),
)
bar = Table(
'bar', meta,
Column('id', None, ForeignKey('foo
On 7/26/2010 4:55 PM, Faheem Mitha wrote:
Hi,
It turns out my example was too hasty. I should have had something like
foobar = Table(
'foo', meta,
Column('id', Integer, nullable=False, primary_key=True),
)
bar = Table(
'bar', meta,
Column('
Hi,
It turns out my example was too hasty. I should have had something like
foobar = Table(
'foo', meta,
Column('id', Integer, nullable=False, primary_key=True),
)
bar = Table(
'bar', meta,
Column('id', None, ForeignKey('foo.id', onupdate='CASCADE',
ondelete='CASCADE'),
