2024 10 29 add protection tube distant control cable

[sjib]

Should solve #387

[kandre]

@sjib I am applying the changes from this PR to a test version of my installed model. I executed the SQL scripts in the sequence specified by init_qwat.sh.

While running 03_qwat_db_organisation.sql, I encountered the following error:

ERROR: relation "value_list_base" already exists

What would you recommend in this situation?

[sjib]

@kandre That is the point that I have to fix first with two conflicting version of value_list_base.

You can test on tww or tdh

[kandre]

Do you think you'll be able to resolve this soon?

I'm concerned I won't be able to test it quickly on tww and tdh due to the time-consuming process of installing or migrating the models, which conflicts with my current schedule. Has anything changed on that front?

[sjib]

@kandre can you try again?

[sjib]

• Add delta files

[sjib]

HINWEIS: Bezeichner »pkey_qwat_vl_sia405pt_protection_tube_horizontal_positioning_code« wird auf »pkey_qwat_vl_sia405pt_protection_tube_horizontal_positioning_co« gekürzt

[sjib]

@kandre There is already a class remote that includes télécommandes:

Isn't this overlapping the content of cable_de_control à distance?

[sjib]

[sjib]

[sjib]

First visualisation protection_tube

test3_karte_protection_tube.pdf

[kandre]

First visualisation protection_tube

test3_karte_protection_tube.pdf

Yes that works for me.

[kandre]

@kandre There is already a class remote that includes télécommandes:

Isn't this overlapping the content of cable_de_control à distance?

Yes it is overlapping and I think we should deprecated it.

[kandre]

@kandre There is already a class remote that includes télécommandes:

Isn't this overlapping the content of cable_de_control à distance?

Yes it is overlapping and I think we should deprecated it or replace it.

[sjib]

@ponceta Is this a good form to provide demodata for sia 405 protection tube and control cable?
Is the header needed or can we go just with the INSERTS?

--
-- PostgreSQL database dump
--

-- Dumped from database version 15.7
-- Dumped by pg_dump version 15.3

-- Started on 2025-04-15 15:32:58

SET statement_timeout = 0;
SET lock_timeout = 0;
SET idle_in_transaction_session_timeout = 0;
SET client_encoding = 'UTF8';
SET standard_conforming_strings = on;
SELECT pg_catalog.set_config('search_path', '', false);
SET check_function_bodies = false;
SET xmloption = content;
SET client_min_messages = warning;
SET row_security = off;

--
-- TOC entry 5027 (class 0 OID 430210)
-- Dependencies: 390
-- Data for Name: sia405cc_cable_point; Type: TABLE DATA; Schema: qwat_od; Owner: postgres
--

[ponceta]

@ponceta Is this a good form to provide demodata for sia 405 protection tube and control cable? Is the header needed or can we go just with the INSERTS?

--
-- PostgreSQL database dump
--

-- Dumped from database version 15.7
-- Dumped by pg_dump version 15.3

-- Started on 2025-04-15 15:32:58

SET statement_timeout = 0;
SET lock_timeout = 0;
SET idle_in_transaction_session_timeout = 0;
SET client_encoding = 'UTF8';
SET standard_conforming_strings = on;
SELECT pg_catalog.set_config('search_path', '', false);
SET check_function_bodies = false;
SET xmloption = content;
SET client_min_messages = warning;
SET row_security = off;

--
-- TOC entry 5027 (class 0 OID 430210)
-- Dependencies: 390
-- Data for Name: sia405cc_cable_point; Type: TABLE DATA; Schema: qwat_od; Owner: postgres
--

This depends mainly on the context but if it is meant to be used in a Sql Query in a db management program like pgAdmin, dBeaver or even QGIS db manager, INSERT statements are more than sufficient.

We could provide some way to alterate and extend the demo data (actually it is mainly static and only updated by deltas for the upgrade process control.)

[ponceta]

@sjib with the latest evolution #394, you are now able to download the datamodel artefact as a product of the CI,

[sjib]

@ponceta Any idea why the CI fails - did we progress on this?

[ponceta]

I fixed it august 6th, #403 artefact should again be available.