Hi, We have some functionality where some identifiers are pushed down into child tables for the purposes of enforcing a unique constraint that would otherwise not be as simple to enforce. What happens is that during an update to a parent table, a trigger runs that pushes the update down to it's child, which may cause another trigger to invoke and push this update further down, so on and so on. It seems, however, that after a flush, FetchedValue() does not cause this value to be fetched (and I believe that this is because FetchedValue() only applies to the object on which it is set). I'm wondering what approach I might take here to get these linked tables to expire in a manner that is centralized and doesn't require users to explicitly require certain objects (or all objects).
-Ryan -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/CAHUie2463tG0QP0NhgvT7PW1sa0%2Byigjg1OGCtfxJimC4g9Hpg%40mail.gmail.com.
