track statement over time

[chadwhitacre]

See also goal (#141) and last_{bill,ach}_result (#342).

[dowski]

I can see a bunch of changes happening early on in the life of a statement. I write something, hit submit, look at it, tweak it, hit submit, look at it, fix a typo, etc.

I think it's fine to write all those to the db, but the actual query for "statements over time" or whatever shouldn't take all of those into account. Maybe use a granularity of "last statement change in 24 hours" or something. Not sure how to express that in SQL.

Does that make sense?

[chadwhitacre]

Yeah, that makes sense. Reminds me of "debounce":

http://arduino.cc/en/Tutorial/Debounce

[chadwhitacre]

The first task is to reimplement the existing UI with the new schema. For that we only need to query the latest value.

[chadwhitacre]

Closing in favor of #1549.