On Feb 27, 2015, at 4:48 PM, Eric Smith e...@esmithy.net wrote:
To those more experienced than me, does this behavior make sense? If so,
could you further my education with an explanation?
If I change an attribute, is_modified returns True (as expected).
If I then reference a
On Feb 26, 2015, at 5:56 AM, Julien Cigar jci...@ulb.ac.be wrote:
On Wed, Feb 25, 2015 at 06:10:55PM -0500, Michael Bayer wrote:
Julien Cigar jci...@ulb.ac.be wrote:
On Thu, Feb 19, 2015 at 11:31:10AM -0500, Michael Bayer wrote:
Julien Cigar jci...@ulb.ac.be wrote:
On Thu, Feb
On Friday, 27 February 2015 09:52:36 UTC-6, Simon King wrote:
On Fri, Feb 27, 2015 at 3:34 PM, Christopher Singley ch...@singleys.com
javascript: wrote:
I'm using the latest dev version of sqlalchemy against postgresql-9.4.1
I can't get SA to apply table-level CHECK constraints
To those more experienced than me, does this behavior make sense? If so,
could you further my education with an explanation?
If I change an attribute, is_modified returns True (as expected).
If I then reference a relationship, is_modified returns False (unexpected).
My output for the following
