Context Navigation

Changes between Version 1 and Version 2 of Ticket #36261, comment 1

-              v1
+              v2
 Not an expert but I think this might cause more harm than good as it basically ignore the specified collation on the column?
+For anyone running into this problem you can register field instance lookups to work around the problem
+{{{#!python
+from django.db.models.lookups import Contains, IContains
+class Foo(models.Model):
+    bar = models.TextField(db_collation="und-u-ks-level2")
+# See https://docs.djangoproject.com/en/5.1/howto/custom-lookups/#a-lookup-example
+class NonDetermisticContains(Contains):
+    def as_postgresql(self, compiler, connection):
+        lhs, lhs_params = self.process_lhs(compiler, connection)
+        rhs, rhs_params = self.process_rhs(compiler, connection)
+        params = lhs_params + rhs_params
+        return f'{lhs} COLLATE "default"' LIKE {rhs}', params
+Foo._meta.get_field("bar").register_lookup(NonDetermisticContains)
+}}}