Modifying values in-place that are already inserted into MemDB is not supported behavior

[ApisecCopilot]

i have a question abort txn.Insert() function. it has a describe “Modifying values in-place that are already inserted into MemDB is not supported behavior.”

` // Create a new data base
db, err := memdb.NewMemDB(schema)
if err != nil {
panic(err)
}
txn := db.Txn(true)
p := Person{"[email protected]", "Joe", 30}
if err := txn.Insert("person", p); err != nil {
panic(err)
}
txn.Commit()

txn = db.Txn(false)
defer txn.Abort()

p.Name = "Janeeeeeeeeeeeeeeeeeeeeeeeeeeeeee"
p.Age = 1111111
p.Email = "[email protected]"

// List all the people
it, err := txn.Get("person", "id")
if err != nil {
	panic(err)
}
for obj := it.Next(); obj != nil; obj = it.Next() {
	x := obj.(Person)
	fmt.Printf("  %+v\n", x)
}

`
aftern Insert and commit, i change object'value
and result is : &{Email:[email protected] Name:Janeeeeeeeeeeeeeeeeeeeeeeeeeeeeee Age:1111111}

is that correctly?

[i4ki]

This behavior is documented here:

go-memdb/memdb.go

Lines 24 to 28 in 0f077dd

	// Objects inserted into MemDB are not copied. It is **extremely important**
	// that objects are not modified in-place after they are inserted since they
	// are stored directly in MemDB. It remains unsafe to modify inserted objects
	// even after they've been deleted from MemDB since there may still be older
	// snapshots of the DB being read from other goroutines.

you have to implement a "copy" strategy for each data structure if you intend to modify them.