I have an IList where the members are strings. I used the configuration below and it created the tables as I would have expected, but my collection is not saving.



I debugged the code and found that in Cascades.cs (line 576)
the following line evals to "false"

if ( elemType.IsEntityType || elemType.IsObjectType || elemType.IsComponentType )
{
CascaedCollection(...) }

My other collections (e.g. one-to-many, many-to-many) are persisting but none of my "element" collections are.

Any help would be greatly appreciated.

Thanks,
Will

I was able to resolve my problem by calling Flush after my Save.

However, as I read the about @cascade options (7.7.1. Lifecycle objects), I expected "all" to persist my child collection without an explicit Flush. Am I incorrect?

Also, the Flush filled in all of my foreign keys to my parent object for other collections that were already persisting on Save. They were persisting, but neither the index nor key were being populated. Flush took care of that as well.

Regards,
Will

Yes you have to call Flush to have your changes persisted. Flush is also called implicitly before executing queries and during transaction commit, subject to ISession.FlushMode setting.

That some objects are persisted on Save is an exception rather than the rule, it happens only for objects using "identity" id generator, because Save has to return the ID of a new object, and so it has to write the object to the database.