Fixes #11

Avoid creating a foreign key when a composite-id contains many-to-one association

Author: RogerKratz

Src/NHibernate.Envers/Configuration/Metadata/BasicMetadataGenerator.cs

@@ -109,7 +109,6 @@ public void AddKeyManyToOne(XElement parent, PropertyAuditingData propertyAuditi
 				  MetadataTools.AddKeyManyToOne(parent, propertyAuditingData.Name, type.ReturnedClass.AssemblyQualifiedName) : 
 				  MetadataTools.AddManyToOne(parent, propertyAuditingData.Name, type.ReturnedClass.AssemblyQualifiedName, true, false);
 			MetadataTools.AddColumns(element, value.ColumnIterator.OfType<Column>());
-			// A null mapper occurs when adding to composite-id element
 			mapper?.Add(propertyAuditingData.GetPropertyData());
 		}
 	}

Src/NHibernate.Envers/Configuration/Metadata/MetadataTools.cs

@@ -74,6 +74,7 @@ public static XElement AddKeyManyToOne(XElement parent, string name, string type
 		{
 			var manyToOneMapping = new XElement(CreateElementName("key-many-to-one"),
 				new XAttribute("name", name),
+				new XAttribute("foreign-key", "none"),
 				new XAttribute("class", type));
 			parent.Add(manyToOneMapping);
 			return manyToOneMapping;

Src/ReleaseNotes.txt

@@ -2,6 +2,7 @@
 
 ** Bug
 * #9 More then one save in transaction with one-to-one relations throw exception
+* #11 Avoid creating a foreign key when a composite-id contains many-to-one association