composite type from being mutated [ticket:1213].
- Repaired support for "passive-deletes" on a many-to-one
relation() with "delete" cascade. [ticket:1183]
+ - Fixed bug in composite types which prevented a primary-key
+ composite type from being mutated [ticket:1213].
+
- Added more granularity to internal attribute access, such that
cascade and flush operations will not initialize unloaded
attributes and collections, leaving them intact for a
params[col.key] = prop.get_col_value(col, history.added[0])
if col in pks:
if history.deleted:
- params[col._label] = history.deleted[0]
+ params[col._label] = prop.get_col_value(col, history.deleted[0])
else:
# row switch logic can reach us here
- params[col._label] = history.added[0]
+ params[col._label] = prop.get_col_value(col, history.added[0])
hasdata = True
elif col in pks:
params[col._label] = mapper._get_state_attr_by_column(state, col)
g2 = sess.query(Graph).get(Version(1, 1))
eq_(g.version, g2.version)
+
+ # test pk mutation
+ g2.version = Version(2, 1)
+ sess.flush()
+ g3 = sess.query(Graph).get(Version(2, 1))
+ eq_(g2.version, g3.version)
+ # test pk with one column NULL
# TODO: can't seem to get NULL in for a PK value
# in either mysql or postgres, autoincrement=False etc.
# notwithstanding