As I mentioned in my original post, I don't want to use citext or lower().
I tested on Windows, but as I mentioned in one of my first posts, collation
and case sensitivity are separate things.
With this, we are back at the beginning of the circle, so I'll leave it
there.
Maybe I'll check back in
To be honest, the reason I don't want to use citext and lower(), is me
being lazy. If I have to use these features, there is more work for me
converting from SQL Server to Postgresql. I have to make more changes to my
database, and more to my software.
But, developers are generally lazy, so you
Desired behaviour:
1. If there is a row with 'ABC' (in a unique column) in the table, a row
with 'abc' should not be allowed
2. If I do SELECT * FROM aTable WHERE aColumn = 'ABC', I should see a row
with 'abc' as well (if there is one in the table)
This has been described in this mailing list a
(with
122 tables).
Regards,
Marcel van Pinxteren
to investigate).
Met vriendelijke groet,
Marcel van Pinxteren
--
Volg onze bouw op http://nieuwekampen.blogspot.com
On Wed, Jan 16, 2013 at 8:14 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Marcel van Pinxteren marcel.van.pinxte...@gmail.com writes:
Therefore the question
