I tried to make sense of the Gargantext.Database.Prelude module. The results of my investigation can be found here.

Most names do not mean anything, and the grouping of constraints often makes no obvious sense. Grouping constraints this way may save a few characters over the project, but it adds a mandatory level of indirection (one cannot make sense of a given one of those constraints referred to somewhere else without looking it up here) and confusion.

I suggest we make a list of the groups of constraints that do make sense, give them a meaningful name, and get rid of the other ones, replacing them by their definition at call site.