0
2

[–] logos_ethos 0 points 2 points (+2|-0) ago  (edited ago)

@PuttItOut Use the citext extension (CREATE EXTENSION citext;) and citext data type if case insensitive matching is needed at the index or SQL level by default. Or use expression indexes with lower function (but you need this in every case insensitive query).

Here is a patch for the SQL files:

voat-citext.patch https://filetea.me/n3woeqSt4vKRregB0vXc0112g

Also, once you have applied that patch, you may want this one if you want time stored in absolute time / UTC instead of "wall clock time." See this: http://phili.pe/posts/timestamps-and-time-zones-in-postgresql/

voat-tz.patch: https://filetea.me/n3wtAeS205BTD6qDfR7WBxyLw

0
1

[–] logos_ethos 0 points 1 point (+1|-0) ago 

Hi @PuttItOut

I am pinging you just to let you know that I fixed the citext patch link (I guess it expired) and added the tz patch if you want it.

0
3

[–] PuttItOut 0 points 3 points (+3|-0) ago 

I don't remember what the reason was that we chose to not go with citext. There was some reason. I'm willing to look into this again but if I recall correctly there was a deal breaker.

@FuzzyWords, do your remember if you talked me out of this or I did that myself?

0
2

[–] PuttItOut 0 points 2 points (+2|-0) ago 

This is a great bug. I love it.

0
1

[–] Germ22 0 points 1 point (+1|-0) ago 

i was going to post our findings here last night, but figured the case sencitivity of voutgres was already known.
it is very interesting how sensitive and far reaching this issue ended up being.
so sofar, the only thing i know that is not case sensitive are the usernames.

0
1

[–] MadWorld [S] 0 points 1 point (+1|-0) ago 

Our submissions to originally separated subverses are also been merged into a single subverse. I think that means putt is very close to fixing the issues with case sensitivity.

0
1

[–] PuttItOut 0 points 1 point (+1|-0) ago 

This should be fixed now, but I haven't tested this in regards to previously created subs. By fixing the creation of subs that differ only by casing, this problem should be resolved.

@PeackSeeker

0
0

[–] 10328901? ago 

I agree, for all intents and purposes this should be FIXED.

0
1

[–] 10281203? 0 points 1 point (+1|-0) ago 

Are you saying you have a subverse (e.g. /v/A) modded by /u/A and another subverse (/v/a) modded by /u/a, and that /u/a is showing up as the moderator of /v/A and vice versa?

I think I can safely just mark this BUG though because I suspect all case sensitivity is going to be removed eventually.

0
1

[–] MadWorld [S] 0 points 1 point (+1|-0) ago 

Yes, the individual owners/mods who created those case sensitive subverses are been merged as if those subverses were a single entity.

0
1

[–] 10281430? 0 points 1 point (+1|-0) ago 

Weird. I suspect this will be fixed when other case sensitive issues are fixed.