Skip to content

Merge 5.2.6 #2205

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
merged 15 commits into from
Oct 4, 2019
Merged

Merge 5.2.6 #2205

merged 15 commits into from
Oct 4, 2019

Conversation

fredericDelaporte
Copy link
Member

@fredericDelaporte fredericDelaporte commented Sep 8, 2019

This PR is not meant to be merged. For having a clean merge, it will be better to directly push to master.

hazzik and others added 13 commits April 16, 2019 00:17
- Combine cahce hit/miss logs where possible

Fixes nhibernate#2127
* Add helper methods to get the configured connection string
* Expand NH-3426 tests to expose nhibernateGH-2110 (and nhibernateGH-2109)
* Detect BinaryGuid setting and apply correct GUID-to-string expression
* Document the new sqlite.binaryguid setting

BinaryGuid is a configuration property of some MySql drivers, but relates to type used in the database for handling GUIDs, which impacts the dialect.

The cases for nhibernateGH-2109 are marked as ignored for now, as that is not a regression.

Fixes nhibernate#2110
This fix the generation bug which previously had to be reverted after
each generation, see maca88/AsyncGenerator#133.
@@ -1081,6 +1081,20 @@ in the parameter binding.</programlisting>
</para>
</entry>
</row>
<row>
<entry>
<literal>sqlite.binaryguid</literal>
Copy link
Member Author

Choose a reason for hiding this comment

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

This new setting lacks its declaration in nhibernate-configuration.xsd file. Thus, it cannot be used in configuration files, and can only be used programmatically. Fixing this is just one line to add into nhibernate-configuration.xsd.
Ideally, it should be done on 5.2.x. But I do not think it deserves a release on its own. So I propose to handle it with a PR targeting master, and waiting for 5.3. If we have a 5.2.x to do for some other reasons before, we could then retarget 5.2x. Otherwise just fix it for 5.3. @oskarb

@fredericDelaporte

This comment has been minimized.

maca88 added a commit to maca88/nhibernate-core that referenced this pull request Sep 10, 2019
maca88 added a commit to maca88/nhibernate-core that referenced this pull request Sep 25, 2019
@fredericDelaporte fredericDelaporte changed the title WIP - Merge 5.2.6 Merge 5.2.6 Sep 29, 2019
Copy link
Member Author

@fredericDelaporte fredericDelaporte left a comment

Choose a reason for hiding this comment

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

This PR is still not meant to be directly merged. For having a clean merge, it will be better to directly push to master.

But now I consider we can do it, and I am just awaiting validation from review.

(For allowing the direct push to master, better not have anything else merged prior to this PR, otherwise I will have to do the merge again.)

# Conflicts:
#	Tools/packages.config
#	src/NHibernate.Test/SystemTransactions/SystemTransactionFixture.cs
#	src/NHibernate.Test/TestDialects/PostgreSQL83TestDialect.cs
#	src/NHibernate/Async/Cache/NonstrictReadWriteCache.cs
#	src/NHibernate/Async/Cache/ReadOnlyCache.cs
#	src/NHibernate/Async/Cache/StandardQueryCache.cs
#	src/NHibernate/Async/Multi/QueryBatchItemBase.cs
#	src/NHibernate/Cache/NonstrictReadWriteCache.cs
#	src/NHibernate/Cache/ReadOnlyCache.cs
#	src/NHibernate/Cache/StandardQueryCache.cs
#	src/NHibernate/Loader/JoinWalker.cs
#	src/NHibernate/Loader/Loader.cs
#	src/NHibernate/Multi/QueryBatchItemBase.cs
@fredericDelaporte
Copy link
Member Author

Review comments have been addressed.

@hazzik hazzik merged commit c79ea1f into nhibernate:master Oct 4, 2019
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.

6 participants