Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Erreur SQL lors de l'import des parcelles #151

Open
Gustry opened this issue Feb 18, 2022 · 0 comments
Open

Erreur SQL lors de l'import des parcelles #151

Gustry opened this issue Feb 18, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@Gustry
Copy link
Member

Gustry commented Feb 18, 2022

Algorithme "Mise en place des données parcellaires pour les certificats de numérotation"

INSERT INTO adresse.parcelle(id,commune, prefixe, section, numero,
contenance, arpente, geom)
SELECT p.parcelle AS id, pi.nomcommune, p.ccopre, p.ccosec,
p.dnupla, pi.contenance,
CASE WHEN p.ccoarp = 'A' THEN True ELSE False END as arpente,
pi.geom
FROM cadastre_module_adresse.parcelle_info pi
JOIN cadastre_module_adresse.parcelle p ON p.parcelle=pi.geo_parcelle
ON CONFLICT (id) DO UPDATE SET
commune=EXCLUDED.commune,
prefixe=EXCLUDED.prefixe,
section=EXCLUDED.section,
numero=EXCLUDED.numero,
contenance=EXCLUDED.contenance,
arpente=EXCLUDED.arpente,
geom=EXCLUDED.geom
renvoyé 0 [ERREUR: la colonne pi.contenance n'existe pas
LINE 5: p.dnupla, pi.contenance,

Le champ n'est pas la en effet sur la documenation : https://docs.3liz.org/QgisCadastrePlugin/database/tables/parcelle_info.html

Est-ce que le contenu de cette table change suivant si on importe MAJIC ?
cc @mdouchin @rldhont

@Gustry Gustry added the bug Something isn't working label Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant