Changes between Initial Version and Version 4 of Ticket #30248


Ignore:
Timestamp:
Mar 13, 2019, 8:58:35 AM (6 years ago)
Author:
Stuart Axon
Comment:

Cheers, I did send an initial mail to the dev list, but think it might have got eaten as I didn't see it (also had a bit of bad luck updating this ticket, updating the description, not leaving a comment).

One thing I found out, is that even with COLLATE NOCASE sqlites regexes don't default to case insensitive, so that would need some support at the django end.

I had a bit of a look into how the postgres citext works, but couldn't work out how to make Operators that integrate with Django in the same way. I guess a really tiny implementation, as fields.py might be a start ?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #30248

    • Property Component Uncategorized → Database layer (models, ORM)
    • Property Resolution → needsinfo
    • Property Status new → closed
    • Property Version 2.1 → master

  • Ticket #30248 – Description

    initial v4  
    1 Sqlite supports case insensitive fields by setting COLLATE NOCASE.
    2 
    3 This works as you would expect for SELECT and INSERT.
    4 
    5 
    6 It would be great to have equivalents to the CIText fields in postgres.contrib - this would make it a lot easier to unit test code using those fields.
Back to Top