It has the significant disadvantage of losing synchronization with the core
so there would be more disparity between the different packages in the
NHibernate universe. For example, has the PostgreSQL dialect been updated
to work with NH 4.2 yet? If they're all secondary citizens, you'll
probably get one or two that get pulled along and the others will stagnate,
making it a far greater task to use a different database since you'll have
to contribute patches and wait for a release or make your own packages.
It also loses the simplicity of needing just one package to perform the
basic operations.
Myself, I think the loss of simplicity outweighs the benefits derived from
separate release cycles.
Patrick Earl
On Sun, Mar 3, 2013 at 8:19 PM, Alexander I. Zaytsev <[email protected]>wrote:
> Hi everyone,
>
> I think it will be extremely useful to have separate distribution for
> dialects/drivers. I see some advantages of this:
>
> - shorter development cycle for dialects/drivers, it means we can deliver
> fixes end enhancements much quickly
> - better integration with ADO.NET providers, as we will not need to use
> reflection
>
> What do you think?
>
> --
>
> ---
> 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 [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
---
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
