duplicated updated generic attributes
fixes #7407
fixes a bug that would cause duplicated attributes on nodes when adding an attribute to a generic schema that the node inherits from. the problem is that the node.attribute.add migration was run for both the node and generic schemas, which can result in 2 new attributes with the same name. this is not guaranteed to happen and the NodeAttributeAddMigration actually contains logic to avoid this issue, but it the problem can still occur if multiple migrations adding the same attribute to overlapping groups of nodes run at the same time because they run inside of transactions and if both cypher queries start before the other is committed, then they will create duplicates.
also fixes an unrelated bug in the NodeCreateAllQuery that was found during testing
TODO:
- add migration
Summary by CodeRabbit
-
Bug Fixes
- Resolved an issue where duplicate attributes could be created when updating generic schemas with new attributes
- Improved attribute handling for inherited schemas to prevent duplicate attribute creation
-
Migrations
- Added graph schema migration (v40) to identify and clean up any existing duplicate attributes while maintaining data consistency across all branches