In the POST, UPDATE front operations, encode slices of pointers and decode at the back (even if targets are not yet synchronized).

[thomaspeugeot]

Steps

• [ ] Manual
  • [x] Back : During Commit, have Slice of Pointers encoding performed with the new slice of pointers encoding in slice of int
  • [x] Front : have Slice of Pointers decoded from slice of int
  • [ ] Front : Commit, have slice of pointers fields encoded into slice of int
  • [ ] Front : Commit, have pointer encoded into an int
  • [ ] Back : Checkout, have slice of pointers fields decoded from slice of int
  • [ ] ~Back : Remove reverse pointers encoding~
  • [ ] ~Front : Remove reverse pointers encoding~
• [ ] Automatic

For instance, in the table stack:

table

the front shuffle the rows. One UPDATE of the table will be enough to update the back.

   const promises = []
    let index = 0
    for (let row of this.selectedTable?.Rows!) {
      row.RowPointersEncoding.Table_RowsDBID_Index.Int64 = index++
      promises.push(this.rowService.updateRow(row, this.DataStack))
    }

will be replaced with the table update

in the form,

the formFieldSelect.Value = optionwill be set automaticaly. No need for formFieldSelect.FormFieldSelectPointersEncoding.ValueID.Int64 = option.ID

svg

    this.svg.SVGPointersEncoding.StartRectID.Valid = true
    this.svg.SVGPointersEncoding.StartRectID.Int64 = startRectangleID

    this.svg.SVGPointersEncoding.EndRectID.Valid = true
    this.svg.SVGPointersEncoding.EndRectID.Int64 = endRectangleID

    this.svgService.updateSVG(this.svg, this.GONG__StackPath).subscribe(
      () => {

(to be investigated) When there is a full commit of the front, the back instances might not be synchronized yet, but the second stage of the commit will redeem with the correct pointers