GlobalSearch | Enhance KeePass search functionality to search | Plugin library

You could use JpaSpecificationExecutor.

In order to use it, you have to extend your repository interface from JpaSpecificationExecutor:

To optimise a query like this against a database there are a few rules to try and follow

• Make sure the query is passed through to the database, do not operate in memory
• Remove or reduce the use of functions
• Don't bother comparing nulls
• Split the query into multiple parallel queries
• Improve the structure to optimise the query

The general idea is that you want to make your comparison directly in the index entries, function or conversions on records in the database will not use the indexes. Databases are specifically optimised to query against Indexes, so it will be important to also create the necessary indexes on your search columns.

You have tagged this as linq-to-sql so we assume that your query is being passed through to the DB, it is important that you make sure it does. The following code and advice will only work if the LINQ expression is a genuine IQueryable that will be resolved into SQL.

1. If your database uses a CASE INSENSITIVE collation, then you can drop all the .ToLower() function calls, you want to avoid function calls so any indexes can be accessed directly.

   • Event though C# is sensitive to case by default, if the LINQ query is translated to SQL then it will obey to collation settings for standard LIKE '%' + @param + '%' comparison.

2. Skip the null comparison, just like the .ToLower() it is not necessary in SQL to check the nullability of a field first before executing a comparison on that field.

This is already a far better filter:

after spending days on this issue I got that there are some nested form which is causing this issue the above code is okay and I am keeping this question as well so that anyone else should not go through this type of problem. JSF not allowing nested forms need to show that error.

If you want to get the response of the tow apis in the same time use Promise.allSettled(promises)

No, it's not the the dimension problem. Although we can not reproduce the error due to incomplete code, the error message is clear:

Supplied objective function must return a scalar value.

Tyr call F with a static vector and check the size of its results. It should return a single value.

But there are also warnings about upper/lower bounds:

In order to achieve what I needed, I made some changes in the Datatable inizialization script and in the ss-books-get controller.

Datatable Inizialization:

I think the issue is with the mocking of selector using provideMockStore. I can see that you have used a lot of this.selectedRows.length (such as in setEditBackgroundColor()) which is being set based on the ngRx Selector.

You can try the search method of js

UPDATED=====

I was having a circular reference (self-reference more accurately) indeed.

I've come up with a workaround that consists of making the @DBRef of attributes, lazy=true, and implementing a custom serializer of the class Term, wich has the self-reference (or circular reference). The reason of implementing the custom serializer, is that I can save a set of the objects that have already been serialized, and if I have to seralize an object again, I just don't.