Skip to content
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

Provide more expressive exception for projections without properties. #1896

Closed
wants to merge 3 commits into from

Conversation

schauder
Copy link
Contributor

Closes #1813

@schauder schauder requested a review from mp911de September 24, 2024 06:59
@schauder schauder assigned schauder and mp911de and unassigned schauder Sep 24, 2024
@schauder schauder changed the title Provide more expressive excepiton for projections without properties. Provide more expressive exception for projections without properties. Sep 24, 2024
@schauder schauder force-pushed the issue/1813-improve-error-message branch from 7039927 to ae27e23 Compare September 24, 2024 07:22

String sql = SqlRenderer.create(renderContextFactory.createRenderContext()).render(select);

return new ParametrizedQuery(sql, parameterSource);
}

private Select getSelect(SelectBuilder.BuildSelect completedBuildSelect) {
Copy link
Member

Choose a reason for hiding this comment

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

Why is the selection list empty in the first place? I'd assume that we pass-thru ReturnedType.InputProperties without checking whether these are empty.

@schauder schauder closed this Sep 25, 2024
@schauder schauder deleted the issue/1813-improve-error-message branch November 11, 2024 13:01
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.

Dynamic projections for interfaces does not work
2 participants