Re: [Django] #30248: Implement case insensitive fields in Sqlite

[Django]

#30248: Implement case insensitive fields in Sqlite
-+-
 Reporter:  Stuart Axon  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  sqlite citext| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Old description:

> Sqlite supports case insensitive fields by setting COLLATE NOCASE.
>
> This works as you would expect for SELECT and INSERT.
>

> 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.

New description:



--

Comment (by Stuart Axon):

 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 ?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.9b5258eb4846bd6e6cc9a6350c411295%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30248: Implement case insensitive fields in Sqlite

[Django]

#30248: Implement case insensitive fields in Sqlite
-+-
 Reporter:  Stuart Axon  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  sqlite citext| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Hey Nick.

 > If this is possible...

 Oh, good idea.

 If someone wants to tell me that this is on, happy to see this moved into
 the Accepted pile.

 (Not sure what thoughts on a `contrib.sqlite` would be if not... —
 probably leaning towards third-party I'd guess.)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e2bf1fbdf50c15145d1d4bcfbe43c8c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30248: Implement case insensitive fields in Sqlite

[Django]

#30248: Implement case insensitive fields in Sqlite
-+-
 Reporter:  Stuart Axon  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  sqlite citext| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Nick Pope):

 Replying to [comment:1 Carlton Gibson]:
 > At that point I'm wondering if similar isn't supported across all four
 supported backends, in which case would we want to pull the fields out of
 `contrib`...?

 If this is possible, it would then make sense to implement
 {{{CharField(insensitive=True)}}}, with default of {{{False}}}. Perhaps
 this could also work with {{{TextField}}}?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.5fb8bad520b163605ee3653290b2f1f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30248: Implement case insensitive fields in Sqlite

[Django]

#30248: Implement case insensitive fields in Sqlite
-+-
 Reporter:  Stuart Axon  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  sqlite citext| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * status:  new => closed
 * resolution:   => needsinfo
 * version:  2.1 => master
 * component:  Uncategorized => Database layer (models, ORM)


Comment:

 Hi Stuart.

 Short answer, "Yes, maybe". :)

 First off would be proof-of-concept fields, maybe in a third-party
 (similar to exist for MySQL and Postgres already). The `CIText` fields are
 fairly minimal, so there may not be much here.

 Then an approach to the DevelopersMailingList to see if there were
 appetite to include such fields in Django itself. (At that point I'm
 wondering if similar isn't supported across all four supported backends,
 in which case would we want to pull the fields out of `contrib`...?) — The
 issue tracker isn't really the best place for that conversation.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.2d37e044f0a31c3b7d49fe299ef97b62%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.