tree 02ea387df3d8671aeff6d0e252efb7f11b59d00d
parent 8bd45a9232aca6463e88a560c3c0d9efc61de6f8
author John Gemignani <jrgemignani@gmail.com> 1712091801 -0700
committer GitHub <noreply@github.com> 1712091801 +0500
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJmDHKZCRC1aQ7uu5UhlAAAisoQADnyjN/8cmNJNF5zfWChNMgP
 JfDvvtUj3xMgpE/xMaxEOOdJjsUlxQMumJPYK0MRRdRfg1WFVkBxX+nTjAXURvze
 o978H5/T8nAPTzfc/g/8q564FsIqCiBZkMlBMF7AvZWwyEzl8tfo6ISuOCWDf4aB
 xpCuSBXeKGTAqtEv0fBuobqDIqoiBxuUiEyy/XYfZhd/dtO6GBm7Itoa+vwYQrRC
 gYq5S30JCXS/twOPrpxjalK8McvbRczi4rbKdmo2DLNoO0cP9k/ZV07Z8OmJCmwk
 RWOKkVEtx54WW++gUMrPaNATBaa4rdxo6Ql3CyYNCGg13UgVLEZ6BTUkv708n87u
 QhJFdvVWdWP98rcJ2BLMuUXQQO/KeXkbX2/iInrL1jT5l1xnZ6pjqW1mRX9COJ9Z
 bMCMhDKofAK1JqVqrhdFNpZMLR0WLQNb4p8jUZHQtoz1MENyRkcoQiTNOEeNA7qV
 LqeMf0vFjOWmXk5Ry2AiqcN0U+wLkzh3KtT99XYgdVAHMd16jqnnXP9DwJj6Ssr5
 /kDA2v/i4UMpOKLsJYpqmsPCQbeyEzfxg1JQ14URVGqOE32AivXwwnUC9tn43eT+
 vZTsekk81R7QI9AFeOcob6bRKdJMZPxRhPdF0PmTUZKd91GOpm38AcP7EkZfL8J/
 KCprMNjEWXPQ6kmXeT8a
 =i/hD
 -----END PGP SIGNATURE-----
 

Fix Issue 1691 - MERGE incorrectly creates multiple vertices (#1718)

Fixed issue 1691 where MERGE would incorrectly create multiple
vertices. This only occurred when MERGE was being driven by a
previous clause.

NOTE: To be more correct, the issue is with creating duplicate
      paths.

The reason this happened was due to the visibility of tuples that
were created during the MERGE instance. It is not possible to add
them in to be rescanned.

Because of this limitation, it required adding the ability to
MERGE to know what path an instance had already created.

Added regression tests.