The `uploaded` and `modified` labels seem to be empty

[eszter137]

I'd expect them to contain the date/source of the upload and the date of the modification. Or maybe they're not for the users? (Maybe they could be hidden in that case.)

$ abcd summary -p uploaded
$ abcd summary -p modified
$ abcd summary -p username

info.username count: 37160 unique: 1
▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉  37160 es732

derived.username count: 37160 unique: 1
▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉  37160 es732
$

[fekad]

It is a good question of how to handle dates in the query. Which data format should we use? For example, ASE has this nice idea: `` age<1h | not older than 1 hour age>1y | older than 1 year

[eszter137]

Or simply the date like 2019.07.18.? -- For older than a year data, maybe we would still like to know the exact date. It could be combined with regular expressions and we could queary by year (or month) then.

[gabor1]

decision: keep these keys stored as integers. special case them for arithmetic queries : <,=,>, the other operand is a string which is coverted to a date before expression is evaluated. special casing of these keys also needed for summary and show commands, where the integer is converted to a date just for display

[fekad]

the properties now exist, but only as unix integer time stamps.

decision: display them in summaries and "show" commands as real dates, and allow operators > < with a string operand which is attempted to be parsed to a timestamp

[fekad]

The summary shows the dates in %y-%m-%d %H:%M format. The representation of the dates in the query can be resolved by using a function like date("19-02-03") (#75 )