giswater / giswater_dbmodel Goto Github PK

hola, al cargar un archivo con extension inp en qgis con giswater, me genera esta nota:

INSERT INTO vi_timeseries SELECT csv1::character varying, csv2::character varying, csv3:: character varying, csv4:: numeric
FROM temp_csv where source like '%[TIMESERIES]%'
AND fid=239 AND (csv1 NOT LIKE '[% AND csv1 NOT LIKE';%') AND cur_user='postgres'
ORDER BY id>>
función PL/pgSQL gw_fct_importswmm_inp(json) en la línea 434 en execute
no se puede insertar en la vista <<vi_timeseries>>

Hello everybody,
I was trying to use scenario management for rules. I have seen that the process (like demand management using views and export inp), has been started but is not finished. Is it in the road map? (and when?)
Best!

https://github.com/Giswater/giswater_qgis_plugin/issues/762

Hello all,
I have a case study where I use a big precision for pattern (level pattern for water drilling in cm). Pattern factors in table inp_pattern_value are of a type numeric (12,4), that is not enough for these cases. Should it be possible to change the type to get more precision in export?
Best!

Hello
in 3.5.022 version, when having mass inserted values in node and arc, I was trying to create new nodes from QGIS but the sequence of the table node still bigin with initial values so there is an error (node_id is existing).
I did not have this issue before.
I make a correction to restart urn_id_seq with max node_id/arc_id but I wonder if it should not be better to have 2 differents sequences for nodes and arcs.
What do you think about it?

expresión SQL <<NEW.date ilike 'FILE'>>
función PL/pgSQL gw_trg_vi() en la línea 285 en IF
sentencia SQL: <<INSERT INTO vi_timeseries SELECT csv1::character varying, csv2::charcater varying, csv3:: character varying, csv::numeric FROM temp_csv where source like '%[TIMESERIES]%'
AND fis=239 AND (csv1 NOT LIKE '[%' AND csv1 NOT LIKE ';%') AND cur_user='postgres'
ORDER BY id>>
función PL/pgsql gw_fct_import_swmm_inp(json) en la línea 434 en EXECUTE
el registro <> no tiene un campo <>

In the version compatibility matrix

https://github.com/Giswater/giswater_dbmodel/wiki/version-compatibility

seems like "any" postgresql version is supported.

But in the doc

https://giswater.gitbook.io/giswater_manual_es/2.-instalacion-y-puesta-en-marcha

there is a big warning that says that postgresql > 12 is no supported.