author | Sebastian Harl <sh@tokkee.org> | |
Fri, 9 Nov 2012 07:41:06 +0000 (08:41 +0100) | ||
committer | Sebastian Harl <sh@tokkee.org> | |
Fri, 9 Nov 2012 07:41:06 +0000 (08:41 +0100) | ||
commit | 2072e784f2fab50bff6aa25831d14424d0f575ec | |
tree | a7bf466b2d30326dfab552b10bc1e00adfc6df2f | tree | snapshot |
parent | 204a47a5eef2694c4e8105ad68e667446bbf36a0 | commit | diff |
PostRR_update(): Fixed handling of multiple columns in the same table.
Previously, after updating the first column, the next columns would already
find a matching timeslice (by timestamp), thus updating the old value.
Now, all old data will simply be removed (for timeslices which are strictly
older than the new timestamp (by timestamp)). This ensures that all data
related to the old timestamp is removed.
Note: However, this *might* destroy unrelated data as well in case a user
stores additional information in that table. For now, I will simply ignore
that as I don't see any reasonable justification for doing so ;-)
Previously, after updating the first column, the next columns would already
find a matching timeslice (by timestamp), thus updating the old value.
Now, all old data will simply be removed (for timeslices which are strictly
older than the new timestamp (by timestamp)). This ensures that all data
related to the old timestamp is removed.
Note: However, this *might* destroy unrelated data as well in case a user
stores additional information in that table. For now, I will simply ignore
that as I don't see any reasonable justification for doing so ;-)
src/postrr.sql.in | diff | blob | history |