You can login if you already have an account or register by clicking the button below.
Registering is free and all you need is a username and password. We never ask you for your e-mail.
[–]PuttItOut0 points
2 points
2 points
(+2|-0)
ago
I think I was actually fairly upset that PG did not honor collations on the text by default. At this point I'm trying to convert all the areas using a common expression so when/if PG does support native case insensitive text types we can replace these extra functions in code easily.
It will be a while until Voat is ready to use PG for a production database so this isn't the most urgent issue we have. We primarily wanted to support PG so that anyone can run Voat on any software deployment. That was our primary goal for supporting another backend option, and so far we have met that goal.
[–]logos_ethos0 points
2 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 ?).
view the rest of the comments →
[–] PuttItOut 0 points 2 points 2 points (+2|-0) ago
I think I was actually fairly upset that PG did not honor collations on the text by default. At this point I'm trying to convert all the areas using a common expression so when/if PG does support native case insensitive text types we can replace these extra functions in code easily.
It will be a while until Voat is ready to use PG for a production database so this isn't the most urgent issue we have. We primarily wanted to support PG so that anyone can run Voat on any software deployment. That was our primary goal for supporting another backend option, and so far we have met that goal.
I'd love to run some tests on the citext but I don't have time right now to test this out. All of the scripts are located here if you want to help us with this: https://github.com/voat/voat/tree/Core/misc/SqlScripts/PostgreSql
And you bring up another issue, I don't have admin knowledge with PG.
[–] logos_ethos 0 points 2 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 points (+2|-0) ago
[–] PuttItOut 0 points 2 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...