…ter cache trigger This was causing the error "The tuple structure of a not-yet-assigned record is indeterminate". While here, restructure things in the counter and sum cache triggers so that UPDATE statements are not sent for unassociated records.
Add specs for NULL foreign key handling for sum cache and touch triggers as well, though those appear to handle NULL values correctly.
…fied, bump version to 1.0.6 The counter/sum cache and touch triggers did not handle cases where the foreign key was modified previously. This makes it handles those cases. The basic idea is simple. If the foreign key changes, process the row as an insert of the new row and a delete of the old row. While here, DRY up the related code so it is easier to understand.
…a table changes.
… by default.
…ss than 9.0
I made this change a long time ago and forgot to commit it. Better late than never. Bump copyright year while here.