Skip to content

DATACMNS-491 - Add support for configuring null handling hints in Sort.Order. #79

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

Closed
wants to merge 2 commits into from

Conversation

thomasdarimont
Copy link

Null handling hints can now be configured on Order as being either:
NATIVE: we let the data store decide how to order nulls or NULLS_FIRST or
NULLS_LAST.
This is the foundation for custom null-handling in other data store support modules like SD JPA and SD MongoDB.

Thomas Darimont added 2 commits April 25, 2014 15:37
…t.Order.

Null handling hints can now be configured on Order as being either:
NATIVE: we let the data store decide how to order nulls or NULLS_FIRST or
NULLS_LAST.
This is the foundation for custom null-handling in other data store support modules like SD JPA and SD MongoDB.

Original pull request: #79.
thomasdarimont pushed a commit that referenced this pull request Apr 28, 2014
…t.Order.

Null handling hints can now be configured on Order as being either NATIVE (we let the data store decide how to order nulls), NULLS_FIRST or NULLS_LAST.

This is the foundation for custom null-handling in other data store support modules like SD JPA and SD MongoDB.

Original pull request: #79.
odrotbohm added a commit that referenced this pull request Apr 28, 2014
Fixed @since-tags, added author tags where appropriate, fixed copyright header in SortUnitTests. Removed unnecessary formatting line comments. Renamed nullHandlingHint to nullHandling inside Order. Changed builder method signatures to be consistent with with(…) methods defining the direction.

Fixed copy & paste test in SortUnitTests.

Original pull request: #79.
@odrotbohm odrotbohm closed this Apr 28, 2014
@odrotbohm odrotbohm deleted the issue/DATACMNS-491 branch April 28, 2014 09:38
Aloren pushed a commit to Aloren/spring-data-commons that referenced this pull request Jun 20, 2019
When the RefreshEndpoint makes a new Environment it creates a new
ApplicationContext with (hopefully) empty sources. If the user has
set spring.main.sources it won't be empty, so we should take care
to mask it off in the process.

Fixes spring-projectsgh-79
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants