HomoCodens

See https://github.com/christophsax/seasonal/blob/main/R/series.R#L330 I would (naively) have assumed it to return a list of the respective series, similar to how the component series are also represented in the `series` field of...

Allow extending a series backwards?

6

Currently timeseriesdb only allows storing vintages _newer_ than any stored before. This is to prevent manipulation of the past by sandwiching new Vintages into the history. It might however be...

`db_ts_get_last_update` has its uses but recently it has come to light that some use cases actually require the latest stored `validity` i.e. vintage date, not simply the timestamp of when...

add checks on valid_on to read methods

1

`valid_on` must be a vector of length 1 that is either a `Date` or an `yyyy-mm-dd` string. How would we best/most elegantly enforce this?

Default for valid_on breaks on more recent version of dependencies

3

It looks like either `R` 4.x or `RPostgres` 1.4.x translates NA to a boolean instead of NULL, which breaks this default for `valid_on`: ``` # RPostgres plays nicer with NA...

add functions to get stored release dates

2

In timeseriesdb related support I had to do until now by far the most performed action was checking the release date of certain series. We should add functions to get...

option to fail a read if not all series are found

2

In a couple of projects now I've seen code fail after a `db_ts_read(con, some_keys)` because not all series in `some_keys` are present in the resulting list. Rather than have each...

rework store_records

2

The original vision of using this function for all versioned tables did not come true. Therefore: * Rename it * Remove anything from its body that does not have to...

db_ts_find_keys returns a data.table

2

I'd have expected a vector.