"Team" Search option does not work
Closed this issue · 2 comments
ChainGangEvents commented
ChainGangEvents commented
Thank you Edward, issue resolved with RaceDB v3.0.81-20220616100128.
esitarski commented
Hmmm. When I try it, it works (see below).
RaceDB searches the "search_text" field in the team record.
The "search_text" field is "normalized" (all accents removed, all
lowercase). This means that "u with an umlaut" will match a "u", and sort
correctly.
I did notice in the code that the search assumes lowercase text. This has
been fixed in the latest version.
However, as you already tried all the options, my guess is that you tried
that and it didn't work.
The "search_text" field is initialized by RaceDB, however, if you populated
the team field yourself directly without RaceDB, it won't get set.
Did you populate the database directly (say, from your own script), or from
the RaceDB (UI or Import)?
To mitigate this, I added some functions to update the search_text for
Teams and LicenseHolders when RaceDB is launched.
This only adds a second or two to the launch, and almost no time if no
fixes are required.
Available in latest RaceDB.
****
When I search for "lang", I match all teams with Lang in the name.
[image: image.png]
When I search for "-1", I get all the competitors without a team:
[image: image.png]
And when I leave the "Team" field blank, I get everyone:
[image: image.png]
…On Mon, Aug 1, 2022 at 2:18 AM ChainGangEvents ***@***.***> wrote:
The **Team (-1 for Independent) ** option in the *Show Participants* view
does not work. Tried to search for a team and used all options but it does
not work:
RaceDB v3.0.81-20220616100128
Windows 10 Pro 21H2
Firefox 103.0 (64-bit)
[image: image]
<https://user-images.githubusercontent.com/29174207/182084303-82392308-f27d-4345-adef-0d0ccc707e6e.png>
—
Reply to this email directly, view it on GitHub
<#43>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABGXKJ25IQDNYEMMZW7LG3VW5T2RANCNFSM55GKO64Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Edward Sitarski