, 2022 at 11:58:33 AM UTC-7 Mike Bayer wrote:
>
>
> On Tue, Apr 5, 2022, at 1:02 PM, Thorsten von Stein wrote:
>
> I'm currently trying to get my applications ready for SQLAlchemy 2.0. A
> change that has forces code changes in numerous places is the removal of
> the auto
I'm currently trying to get my applications ready for SQLAlchemy 2.0. A
change that has forces code changes in numerous places is the removal of
the automatic addition of new instances to the session upon establishing a
relationship with an object already in the session. In the explanation of
gt; to bypass the result and go straight to the pymysql cursor if you'd like
> to rely upon the driver-specfic behavior, you can get to it as
> result.context.cursor.lastrowid:
>
> with engine.begin() as conn:
> result = conn.execute(messages.insert().values(values))
>
I use SQLAlchemy with MySQL. In one application, I need to obtain the
server-generated primary key values of newly inserted rows by obtaining the
value of the first inserted row with the property inserted_primary_key.
However, after upgrading to version 1.4.15, this property return only
zcomputing.com>
wrote:
>
>
> On 03/16/2016 02:37 PM, Thorsten von Stein wrote:
>
>> For several years, I have been using a pattern for making a many-to-one
>> relationship from *cls* to *remoteCls* with a one-to-many backref with a
>> join condition cls.foreignKey
Great! Thanks a lot.
Thorsten
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to
The following issue, which puzzled for several days, exists in several
versions. I verified that it applies to version 1.0.9
In my understanding, the post_update flag is required on a relationship
between to classes A and B if there is another relationship between B and A
in order to break a
