On Tue, 30 Mar 2021, klaus.hasenbach(a)web.de wrote:
Thank`s Allin!
Now it is obvious that the slow speed of dbnomics 0.4 with or without
metadata is related to the fact that both are using same new API of
dbnomics. [...]
Klaus, did you see my follow-up? The dbnomics API is not the primary
issue with the speed problem, which I think is now solved.
Same problem with the failed statement of a single request as I just
figured out: The installed version of dbnomics 0.4 needs a correct
stated dataset. Monthly data like ECB/IRS/M.IT.L.L40.CI.0000.EUR.N.Z
runs only with a monthly dataset and not with a quaterly dataset. My
installed version of dbnomics 0.2 in gretl 2018c runs with both datasets
without an error.
Not sure I'm understanding the problem. Below are three variants of
loading the series ECB/IRS/M.IT.L.L40.CI.0000.EUR.N.Z, all working
here with gretl's dbnomics 0.41.
# (1) let the dbnomics import create a monthly dataset
clear
open dbnomics
data ECB/IRS/M.IT.L.L40.CI.0000.EUR.N.Z
smpl
# gives: 1993:01 - 2021:02 (n = 338)
# (2) start with a correctly sized monthly dataset
clear
nulldata 338
setobs 12 1993:01
open dbnomics
data ECB/IRS/M.IT.L.L40.CI.0000.EUR.N.Z
# start with a quarterly dataset (automatic compaction)
clear
nulldata 112
setobs 4 1993:1
open dbnomics
data ECB/IRS/M.IT.L.L40.CI.0000.EUR.N.Z
smpl
# gives: 1993:1 - 2020:4 (n = 112)
Allin