Skip to content

Conversation

@krzysztofruszczynski
Copy link

It looks like those count queries are not needed. Even if we provide value, which is not in database, or_where will add 0 records to actual query result and it would be transparent for user. Removing those queries significantly increase performance and reduce number of sql queries. Variable $http is not used as reference anywhere, so its value inside doesn't have further impacts.

…d options exist (final db query uses OR condition so there would be no effect on sql result)
@AllanJard
Copy link
Contributor

Thank you for the PR. I'm not sure about this - I'll need to look in to it more and remind myself why those queries were there in the first place before I merge this in.

@AllanJard
Copy link
Contributor

This is the original commit that introduced that code.

And this was the description of the bug that triggered that addition:

Select a first name in SP
Edit that name in the main table to anything else
Should end up with something like

image

At this point SP should check if any of the selections it wants to make are possible and then redraw completely if not

I agree that there must be a more performant way of doing all of this though.

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