In most cases, participants will be searched for case-insensitively, so the column should be redefined to include COLLATE NOCASE. This should also create a "case-insensitive" index as well, which is good. See this question for more information.
Better yet, maybe create a custom collation that leverages Python's case-folding. Then we shouldn't run into the non-ASCII value issues that the built-in NOCASE does.
In most cases, participants will be searched for case-insensitively, so the column should be redefined to include
COLLATE NOCASE. This should also create a "case-insensitive" index as well, which is good. See this question for more information.Better yet, maybe create a custom collation that leverages Python's case-folding. Then we shouldn't run into the non-ASCII value issues that the built-in
NOCASEdoes.