Skip to content

after an expire on an object with lazy loaded attributes, attributes instances are not updated #492

Closed
@sqlalchemy-bot

Description

@sqlalchemy-bot
Collaborator

Migrated issue, originally created by Anonymous

I have attached a test script that reproduces the problem, with some comments.

I do not know if I used the session.expire correctly, however I think this is a bug of SQLAlchemy.

The output of the script is:

manlio@synapsis:~/projects/bugs/sqlalchemy$ python expire.py
foo instance, x=x and bar=[instance, y=y](bar)
foo instance, x=x and bar=[instance, y=y](bar)
foo instance, x=x and bar=[instance, y=y](bar)

Attachments: expire.py

Activity

sqlalchemy-bot

sqlalchemy-bot commented on Feb 24, 2007

@sqlalchemy-bot
CollaboratorAuthor

Michael Bayer (@zzzeek) wrote:

we never had implemented "refresh-expire" cascade, so this operation never cascaded. i put an initial implementation in changeset:2360 which passes this test and also a basic unit test added.

sqlalchemy-bot

sqlalchemy-bot commented on Feb 24, 2007

@sqlalchemy-bot
CollaboratorAuthor

Changes by Michael Bayer (@zzzeek):

  • changed status to closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingorm

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @sqlalchemy-bot

        Issue actions

          after an expire on an object with lazy loaded attributes, attributes instances are not updated · Issue #492 · sqlalchemy/sqlalchemy