0
2

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

Just use citext. That is what other people do, and there is nothing wrong with it. When PostgreSQL adds case insensitive collations, it will be more transparent to migrate from citext to that than with any other solution. citext will be less painful for you now and in the future when you make the switch.

I have voat-citext.patch and voat-tz.patch. Do you want me to create a github account and create a pull request for both? I am fine with someone else taking those patches (@FuzzyWords ?).

If you want to trust me, I can be that admin.

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

[Deleted]

0
1

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

I am very glad to help. In case you missed it, I created a github account and made a pull request: https://github.com/voat/voat/pull/909 Please use that as I missed an update to data.sql in the .patch file.

0
2

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

It would be easiest to submit this in git that way I can work with it in a controlled way.

@FuzzyWords I'm going to need you to take a look at this thread because I do have a lot of casing bugs on the pile...

0
1

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

Pull request (updated): https://github.com/voat/voat/pull/909