Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ORM  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"278b6187d2a6711afb0b35dc5c3c09fe5be9adb3" 278b6187]:
 {{{
 #!CommitTicketReference repository=""
 revision="278b6187d2a6711afb0b35dc5c3c09fe5be9adb3"
 Refs #21181 -- Corrected DatabaseFeatures.test_collations for Swedish
 collation.

 Previously, backends used different keys "swedish-ci" or "swedish_ci".
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.bc584baff1dcfb88b129872fe32278a3%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ORM  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"63300f7e686c2c452763cb512df9abf7734fd588" 63300f7e]:
 {{{
 #!CommitTicketReference repository=""
 revision="63300f7e686c2c452763cb512df9abf7734fd588"
 Fixed #21181 -- Added Collate database function.

 Thanks Simon Charette for reviews.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.42b8c4a6467a0e64801de83fbc7ea010%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


Comment:

 I added warning to docs.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.ab80b7a872b8f05e45696cabe9f9dbd2%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by felixxm):

 So maybe, we can add a warning in docs, e.g.
 {{{
 To protect against `SQL injection attacks
 `_, ``collation``
 shouldn't be
 a user-controlled parameter because collation names are database
 identifiers and cannot be properly escape.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.633b589f3ee00c330cb92564c9e779a6%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Yes, `quote_name` cannot protect against SQL injections, it shouldn't be
 an issue just like `Func(func)` also allows injections? As long as
 `collation` is not under user control it should not be an issue.

 Since collation names are identifiers and cannot be provided as string
 literals (see comment:11) I don't see a way around that?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.b61bac356c48e41b0e6087b8dd697be7%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.4e86538f3bb53c0e52c680516c864f57%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * stage:  Accepted => Ready for checkin


Comment:

 Went through a few rounds of reviews and patch now LGTM

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.f7044a999dd7cd5020bc373bab283d73%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tom Carrick):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/13284 PR]

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.125ecedeabdcafc6074e7c2539d7c864%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tom Carrick):

 * owner:  Alan => Tom Carrick


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.b954c07ce9d5005ed2082f384d5b066f%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Alan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * cc: Simon Charette (added)


Comment:

 Looks like collation names are identifiers on these backends and need to
 be escaped using `connection.ops.quote_name`. Was MySQL also behaving this
 way?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.24bc6cf7a2947d0c24605bd5da29745b%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Alan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alexandr Artemyev):

 * cc: Alexandr Artemyev (added)


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.fb5b989557df33534b7e2b5d582f6b08%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Alan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tom Carrick):

 * cc: Tom Carrick (added)


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.eef51fc5ffcf61d2cb1ee53c2cea670d%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Alan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tom Carrick):

 I made a quick attempt at implementing `Collate()` as an expression. I've
 hit a problem though, as it seems like SQLIte doesn't allow you to use
 parameters with `COLLATE`:


 {{{
 In [34]: with connection.cursor() as cursor:
 ...: cursor.execute("select name from testapp_foo order by %s
 collate %s", ["name", "nocase"])
 ...: row = cursor.fetchall()

 ...

 OperationalError: near "?": syntax error
 }}}

 I also have problems on postgres (haven't tried with other backends):


 {{{
 In [16]: with connection.cursor() as cursor:
 ...: cursor.execute("select name from testapp_foo order by %s
 collate %s", ["name", "en_US"])
 ...: row = cursor.fetchone()

 ...

 ProgrammingError: syntax error at or near "'en_US'"
 LINE 1: select name from testapp_foo order by 'name' collate 'en_US'
 }}}

 Not exactly sure what's going on here, but it looks like single quotes
 don't do it here. It works if I remove the placeholders and set it with
 `"en_US"` - with double quotes.

 Maybe I'm misunderstanding something.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.a3cb0129e864907278b2aa111e50c8f9%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Alan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Now that `order_by` has proper expression support this is pretty
 straightforward to implement using an `Expression` of `Func` subclass.

 I guess this ticket could be repurposed to allow a `collation` argument to
 be passed to `OrderBy` or introduce a backend agnostic `Collate`
 expression.

 `order_by(F('title').desc(collation='fr_FR'))` or
 `order_by(Collate('title', 'fr_FR').desc())`

 I think a `Collate` expression would make more sense since it could be
 used in lookups as well `filter(title=Collate(Value(title), 'fr_FR'))`.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.be84a877a292079aa44f4fe754585840%40djangoproject.com.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Alan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alan):

 * owner:  (none) => Alan
 * status:  new => assigned


--
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/083.15cd95dae232d2f329cd2c1f8639c2ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ian-Foote):

 * owner:  Ian-Foote =>
 * status:  assigned => new


--
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/083.d89e0d715739a7a2c0ff7a341ad76825%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  Ian-Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ian-Foote):

 * owner:  nobody => Ian-Foote
 * status:  new => assigned


--
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/083.560b3085507305353719294134625b6f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 Now that expressions are in, a Collate expression would be a very welcome
 addition to Django. It should work on all databases that support
 collations, not just on PostgreSQL.

--
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/083.5003455ca11c054d3fc293223d9b64b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  ORM  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by alan.kesselmann@…):

 Hmm i can see you have done loads of work in your custom lookups branch.
 Any idea which version those changes might end up in?

-- 
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/083.5ed342b14d6a14c9808a62c566711d16%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  ORM  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 I tried how hard this would be to implement using custom lookups. Turns
 out it was somewhat straightforward, see:
 
https://github.com/akaariai/django/commit/76063881d79732cbb1942e9905fe4d51c0df09c1

 The example works only on PostgreSQL 9.1 plus, and the test works only if
 collations fi_FI, en_GB and POSIX are available (I believe the last one is
 always there). Of course, adding in full multidb support would require
 more work so that the SQL would actually work on all databases.

-- 
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/083.09fcef68160d7c4b8426a74edbd182ad%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  ORM  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by alan.kesselmann@…):

 I think there is no duplicate to this, as this is relatively new thing.
 #14310 is similar cause it requests per query collation overrides but the
 #9682, which is marked as #14310's duplicate is another thing completely.

 In my test (or investigation) case i created two postgresql databases. One
 with default en_US.utf8 collation and one with POSIX collation. Since one
 table can hold data which is in several languages you (in this case i)
 have to be able to add collation as a part of query. Like this:

 SELECT * FROM  ORDER BY  COLLATE "",
 
 or
 SELECT  COLLATE "" FROM  ORDER BY
 

 What this allows to achieve is that table of strings like:
 id, name
 1, älan
 2, alan
 3, õlan

 will be sorted with query "SELECT * FROM table ORDEr BY name" to
 2, alan
 1, älan
 3, õlan
 with en_US.utf8 collation and to
 2, alan
 3, õlan
 1, älan
 with estonian alphabet based collation.

 Your example, qs.alias(name_fi=Collate('name', 'fi')).order_by('name_fi')
 is the best i think (for my use-case anyway), as it pictures the core
 thing that i need - pair of column name ("name") and collation ("fi"). The
 Collate object seems like a good idea that might allow some more complex
 use cases too (http://www.postgresql.org/docs/9.1/static/collation.html
 lists several).

-- 
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/083.6555d6e5a5ce845b215ce73f43b5adbe%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  ORM  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I agree that some solution to this is a good idea. There are some tickets
 that are close to this request, #14310 and #9682 come to mind. I didn't
 find a perfect duplicate so accepting this.

 Custom lookups could offer a neat solution to this. You should be able to
 do: `qs.alias(name_fi=Collate('name', 'fi')).order_by('name_fi')`. Or, to
 use collated filtering, use `qs.alias(name_fi=Collate('name',
 'fi')).filter(name_fi__icontains='someval')`. See #16187 for details. The
 patch in that ticket already offer all the machinery needed to do this,
 but there is still a lot of work before merge is possible.

 While waiting for custom lookups maybe there should be some other way to
 achieve this.

-- 
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/083.9157c9920042fdd6c86ceff180e332fa%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
-+-
 Reporter:  alan.kesselmann@…|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  ORM  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

 * stage:  Unreviewed => Accepted


-- 
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/083.51bd22c1c85d8ea4f6050b3e8bf11d4a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21181: collation specific query results ordering

[Django]

#21181: collation specific query results ordering
--+
 Reporter:  alan.kesselmann@… |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:
 Severity:  Normal|   Keywords:  ORM
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 There has been feature request for it in 2012 in django-developers group :
 https://groups.google.com/forum/#!topic/django-developers/0iESVnawNAY.
 Before finding that request i asked about same thing in stackoverflow:
 http://stackoverflow.com/questions/18935712/queryset-sorting-specifying-
 column-collation-for-django-orm-query. Both Anssi
 (https://groups.google.com/d/msg/django-
 developers/0iESVnawNAY/JefMfAm7nQMJ) and me outline how it could be used
 im same way:

 .order_by([fieldnames], collation = 'et_EE')

 another version of it could be automatical, based on django language
 settings. Model often has ordering set in its Meta. So why not include
 automatical ordering there too.

 Is it possible to include this into some of next versions of Django?

 '''Some background'''

 If django is used to power some international site like a newspaper then
 there is rarely need for sorting data based on sorting rules of language
 other than english. If you use it to power a site that hosts data in
 several languages then you have need to also display data in that language
 properly. Sorting based on English alphabet does not work correctly in
 that case cause letters missing from english alphabet (and there are MANY
 of those letters that exist in swedish, danish, german, not to mention
 estonian, russian etc. alphabets) are displayed in completely wrong
 places.

 Again - most django sites will be probably using single language. But
 there are many cases that will benefit from this feature. Like e-commerce
 modules, that translate product names - they can benefit from it. Any site
 that allows language based naming or translating of their objects will
 benefit from this feature.

-- 
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/068.a06e3cfa1bcd3e7bf97ec91b86b9db8e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.