Roman Artiukhin

> but if checking the emitted SQL query, we can see that the one-to-one was eagerly loaded. It's about not constrained one-to-one behavior. It's eager loaded to check if association...

> it does not need to know on entity-loading whether the association exists or not So I would call it a missing feature "Lazy loading support for nullable entity with...

Yes that's one possibility. Alternatively to keep NHibernate out of entity I'm thinking of some static class with user provided generator settings for type members (for now with single SkipInitialization...

Are you about this mapping? https://nhibernate.info/doc/nh/en/index.html#mapping-generated No I don't think it's related to this feature. Proxy initialization is required on property access of generated properties (if it's not ID property)...

**fredericDelaporte** [wrote](https://github.com/nhibernate/nhibernate-core/issues/1342#issuecomment-397224187) > In other words the Linq translation should generate a sub-query explicitly here, counting from the paginated query. **hazzik** [wrote](https://github.com/nhibernate/nhibernate-core/issues/1342#issuecomment-397224766) > Subqueries in the from clause are not...

I imagine simple running existing lib for 3rd party driver would lead to various driver/dialect specific test errors. We also need a way to skip not supported tests by 3rd...

> However this will still set the Attributes to null against the products where all the values of the Attributes are null and will likely lead to much bigger problems....

> Linq query OrderBy fails Fails how? Please provide full exception details (exception message + full stacktrace)

> did you need more information on this one? Nope. Should be enough for someone to work on it.

Yes, you are right it's > some kind of leftover Your suggestion looks correct.