I do not care about keeping Iesi or not, I just care on keeping the feature working in a satisfactory way. So with those conditions, it should be alright.
NHibernate already have some own internal specialized collection/dictionary for its internal uses. Why not adding another one. But it should be internal, since this is not the purpose of NHibernate to supply specialized collections to consume. Then if the user needs to instantiate some ordering preserving hashset on his side, it will be up to him to use some adequate implementation, be it Iesi or something else. Le dimanche 19 novembre 2017 00:24:29 UTC+1, Fabio Maulo a écrit : > > Sir, yes sir. > > Can we agree about this: > . The PR should allow the usage of order-by in <set> mapping > . As all other *persistent collection* NH may have its own implementation > to ensure the behavior just when the collection comes from NH > . The user is responsible to use an ISet implementation that maintains the > order when he works on its side > . The PR should pass at least all existing tests > > Is it ok ? > > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to nhibernate-development+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
