Actually, by the countAPI spec, we're actually missing a value on keys:
Countapi ref:
/info/:namespace?/:key
Get information about a key.…
Not sure, it'd probably require a db column that gets written to whenever a column is accessed + another one that has a "allowed time since access" thing or something. Just a ttl column probably…
Actually, by the countAPI spec, we're actually missing a value on keys:
Countapi ref:
/info/:namespace?/:key
Get information about a key. Optionally specify the…
Can we just not return the missing column? (Adding a column that is supposed to update on its own would be a nightmare)
Not sure, but it just seems like a bad idea to allow unauthenticated users to query everything in a db table
Actually, by the countAPI spec, we're actually missing a value on keys:
Countapi ref:
/info/:namespace?/:key
Get information about a key. Optionally specify the namespace. …
What if more things that we don't want to return are added later on, though?
Not really, it'd probably just waste up to two queries on something avoidable
Pretty sure this will always return false (also, true in the response from the db should be a boolean, rather than a string, iirc, and it'd be db_res[0].enable_reset).
It'd be nice to somehow make counter_get optionally return the get_namespace_id response it gets to save a DB query, but that's probably not very important.
Could something like this maybe be used? idk, I might be a bit tired right now.