Quote from: dkincaid on January 05, 2018, 10:13:40 PM

Quote

The biggest problem is the lack of a year. I stretch my browser out to full screen width and still no year. It's a minor thing and your time is better spent on more important things. I'll figure out how to work around it.

Quote

Yes.. it doesnt appear to be a responsive table, the date is never displayed regardless of browser width afaik. Ive been fighting the same issue. The i18n regionality of the timestamp format is not the issue being raised, its that the year is missing, so the year must be assumed in any application consuming this data. In excel using INT() operations against this column, it will assume the current year, which is why folks are hitting this issue now given the new year.

It doesn't matter to me what i18n format you put the timestamp in, but please add the year so this data is precise enough to be consumed in outside applications.

Thanks!

Yes, thank you for saying it better than I was. Adding the year will fix the issue.

Had a think about how to resolve the issue.
Some time (after the new transaction table is complete) I'll add a button on the page to generate a text file page of the contents with the raw data.
So since the page actually already can have that data, if you want it in raw format, a little JS will produce that from the page itself.

I don't really want an API since it's really a once off, once in a rare occasion, that people 'need' the data, not an API to poll regularly.