Skip to content

Conversation

HermanSchoenfeld
Copy link
Contributor

This is a long-awaited feature for many users. Prior pull request had unit test errors. The code has been re-done, all tests pass and has been QA'd on my end.

All mappings are DB-generated in the order they were declared, which is useful for cosmetic purposes as well as some legacy compatibility use-cases.

@jrgcubano
Copy link
Member

jrgcubano commented Dec 19, 2018

@HermanSchoenfeld great work! thanks for this... I will have a look tomorrow. 🥇

I was thinking what level of backward compatibility will this have...

Dictionary.TryGetValue(key, out value);
var removed = Dictionary.Remove(key);
if (removed)
//OnCollectionChanged(NotifyCollectionChangedAction.Remove, new KeyValuePair<TKey, TValue>(key, value));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this unused comment.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed, with other cleanup.

@jrgcubano jrgcubano merged commit 2bc9d05 into nhibernate:master Jan 4, 2019
@hazzik hazzik added this to the v3.0.0 milestone Oct 7, 2020
@hazzik hazzik changed the title Generate all mappings in the order they were declared. Generate all mappings in the order they were declared Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants