Closed thiver closed 9 years ago
It should and I have been aware of this but yet to find a sutable solution for this. I'd be reluctant to put in a hack when a proper fix can be found.
It is indeed just a hack until I can remove it :-)
There is currently no reliable way to detect whether or not the object is the first revision, and any solution we can come up with requires a significant change with BC implications. Moving this to ORM v2.
When I place an Observer_Self on a Temporal Model with the event "after_insert", the event gets called every time a change has been made to an object. So on every new row in the database table, there is an after_insert call. Shouldn't this be limited to the first temporal row of the object only?
I solved the problem with the following hack for now: