Skip to content

Move MsSql constants from driver to dialect. #1610

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

ngbrown
Copy link
Contributor

@ngbrown ngbrown commented Mar 13, 2018

This is a split off from #626 just incase I don't get that fully rebased in time for v5.1. These changes are still valuable, but easy to review.

Also:

  • Fix description of DB2400Driver.
  • Driver code formatting tweaks.

@hazzik
Copy link
Member

hazzik commented Mar 13, 2018

Move MsSql constants from driver to dialect

I don't understand what is the point of doing this.

@fredericDelaporte
Copy link
Member

fredericDelaporte commented Mar 14, 2018

It is required for providing the driver as a separated project, which should be done for allowing people to not rely on reflection under .Net Core/Standard if they wish. (Unless it is considered as something to be supplied externally, but I am not agree with such a view. Supplying drivers with explicit dependencies for most common databases should be done by an ORM in my opinion.)

@fredericDelaporte fredericDelaporte merged commit f693cc8 into nhibernate:master Mar 14, 2018
@ngbrown ngbrown deleted the move-msqsl-constants branch March 14, 2018 12:27
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