Snapping an hydrant on a pipe en vertex does not merge nodes

[haubourg]

When creating an hydrant snapped on pipe extremity, the underlying node is reused to inherit the hydrant. When just snapping an existing hydrant to a pipe end, we still have two nodes, and no way to select by attribute query the hydrante- pipe relations. @3nids is this made on purpose or a design issue?

[3nids]

it's an issue, on a node inherited class move, there should be a new node creation process (if an exisiting one is found, it should be reused). This is an easy test case by the way.

[haubourg]

Planning that to mid 2017 and raising priority

[lbartoletti]

combining qwat_od.ft_element_hydrant_delete() and qwat_od.ft_element_hydrant_insert() into qwat_od.ft_element_hydrant_update() do the job.

@3nids is this trigger generated by metaproject? How to change it? Thanks.

[lbartoletti]

ping @3nids

[lbartoletti]

Denis @3nids ?

[ponceta]

Status of this? If it's an issue it should be corrected (before 1.3.3?)

[3nids]

@lbartoletti yes the triggers are generated automatically (metaproject) But this should not happen at the hydrant but at the network or node level.

[haubourg]

@lbartoletti can you push a fix now ?

[haubourg]

OK, after testing, all installations are also afected. We probably need a gobal business rule to merge nodes when we want to snap to an existing node and merge underlying nodes. This is a big refactoring step, so I postpone the milestone in order to let the 1.3.3 release fly this week.

[tudorbarascu]

@haubourg IMHO it should be considered a bug (very high priority even).