Context Navigation

Changes between Initial Version and Version 1 of Ticket #26610, comment 3

initial	v1
1		My current backend is indeed postgres. In my specific usage - case is important. It's just when users are searching for models in my search box the filter needs to be case insensitive because... well... users are very sensitive about case insensitivity.
	1	My current backend is indeed postgres. In my specific usage case is important. It's just when users are searching for models in my search box the filter needs to be case insensitive because... well... users are very sensitive about case insensitivity.
2	2
3	3	With the {{{citext}}} idea - would programmers have control enough to have both a sensitive and insensitive index if required? Or would that make all filters implicitly case insensitive?