On Monday, May 29, 2017 at 12:27:51 PM UTC-4, Mike Bayer wrote:
>
> I'm assuming this "invalidates the transaction" is on the Postgresql
> side, e.g. you get "current transaction is aborted". There is a simple
> solution for that which is to use a savepoint, which with the ORM is via
>
On 06/05/2017 11:36 AM, alexei.bogda...@ytech.by wrote:
Thanks Mike,
I understand what you're talking about, but still this alchemy machinery
is pretty much ambiguous. For, example:
if SomeClass was a Table instance with Column attributes, this insert
would work successfully:
print
Thanks Mike,
I understand what you're talking about, but still this alchemy machinery is
pretty much ambiguous. For, example:
if SomeClass was a Table instance with Column attributes, this insert would
work successfully:
print sa.insert(SomeClass).values([
{SomeClass.c.service_id:
Hi all,
I have a schema Chapter(One) with a relationship to a Media(Many). Somewhere
down the line we want to add Sermon(One)-Media(Many).
Is just adding a Sermon back reference to Media the best way to expand the
capabilities of Media? Or is there a better way to go about it?
--
SQLAlchemy
On Tuesday, 23 November 2010 01:18:53 UTC+5:30, Dan Ellis wrote:
>
> Thanks for those tips. InstrumentationManager sounded like the best
> thing, so I've gone with that idea. Here's the basic structure of it
> for anyone who's interested: http://pastie.textmate.org/1318179
>
> Thanks again,