You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if it is a desired behavior, but as the title says, when attempting to output to sqlite with read_forecastwith an experiment's name starting with a number, it fails.
I think it is due to sql complaining about tables or columns with names starting with a numeric character without quotation. But I'm not sure since I'm quite new to both R and sql.
I found a workaround by defining a new file_template and renaming the fcst_model as follows
This is because column names are not allowed to begin with an integer in SQLite. The sqlite schema uses <fcst_model> as the root of the column name that stores the forecast data.
As it is the only way around it is to have experiment names that don't begin with an integer, or to change the name via setting fcst_model and a bit of hardcoding in the template like you have done. Unfortunately t's very unlikely that we'll implement a built in way of dealing with such cases as it would either require a complete redesign of the SQLite schema, or changing fcst_model behind the scenes - both of which seem to be quite risky moves.
Hi,
I don't know if it is a desired behavior, but as the title says, when attempting to output to sqlite with
read_forecast
with an experiment's name starting with a number, it fails.I think it is due to sql complaining about tables or columns with names starting with a numeric character without quotation. But I'm not sure since I'm quite new to both R and sql.
I found a workaround by defining a new
file_template
and renaming thefcst_model
as followsI guess I can keep doing it this way if this is an intended behavior.
Thanks!
Jose
In case of interest, the error I was getting was:
The text was updated successfully, but these errors were encountered: