Foreign Keys in the designer

Hi, next question :-)

Why am I getting the following error:

• Create an address table with a primary key (Id)
• Create a customer table with a column called AddressId
• Add a foreign key from Customer.AddressId to Address.Id
• Drag onto the designer from the server explorer
• Use Fluent to configure the session factory to cascade saves by default
• Create a new address object
• Create a new customer object, assigning it the address object
• Try saving the customer object
• Watch in horror as the error message "Error dehydrating property value for NHibernatetest.Customer.Address" appears on your screen.
• Halt execution
• Delete the AddressId field from the customer object in the designer
• Re-run the app, this time it saves fine.
• Check the DB - all is good and the foreign key is what you'd expect it to be.
• Post question on Mindscape's forum
• Get lunch, read Iain M. Banks' new book.

Full error dialog consists of:

Error dehydrating property value for NHibernatetest.Customer.Address
Inner Exception: Make sure that the maximum index on a list is less than the list size
Inner Exception: Make sure the index is not a negative nyumber
Inner Exception: Make sure data column names are correct

Cheers,

Matt.

Hi Matt,

This looks like we are generating an invalid mapping, the AddressId should be being generated with insert='false' and update='false' as the issue is that there are two writable properties mapping to the same column. As you have found, removing the AddressId property removes ones of these and therefore the issue goes away.

I will look at making an update to fix this and let you know once this is available in the nightlies.

Thanks!
Jeremy

Hi Matt,

We have added in an update for this to generate the required attributes with the property and this will be available for you in tonights nightly build.

Jeremy

I found the same problem with dehydrating - it is possible to set some attribute, that would let the insert='false' and update='false' parameters set to be generated?

In my model there are many relations, and I do not want to make the corrections in generated XML by hand...

With regards Aranius

Are you able to send us through a small repro project highlighting this please as we believe this has already been addressed as above.

Thanks!
Jeremy

Hi Aranius,

This looks to be a different scenario to the original issue as you are using a custom type. Ive added an item to our backlog to see if we can add automated generation to cover this but in the meantime you can handle this via a custom code mapping.

e.g.

• Create a new partial class for Ability

• Implement the following:

  static partial void CustomizeMappingDocument(System.Xml.Linq.XDocument mappingDocument)
  {
    var nodes = mappingDocument.Root.Nodes().ToList();
    var idType = ((System.Xml.Linq.XElement)nodes[0]).Nodes().ToList().OfType<System.Xml.Linq.XElement>().Single(e => e.FirstAttribute.Value == "IdType");
  
  
    idType.SetAttributeValue("insert", "false");
    idType.SetAttributeValue("update", "false");
  }
  

This will transform the generated mapping with insert=false, update=false as required to cover this issue. If you have any other instances of this you can use the same approach to customize the generated mapping accordingly.

Jeremy

Hello,

thank you very much for your response. The fix is working, it is just tedious work - I have really big number of tables and 1 to N relations :)

When do you assume implementation of automated generation?

With regards Aranius