#27355: Emphasizes the role of TrigramExtension and UnaccentExtension in the
     Reporter:  Maxime Lorant        |                    Owner:  nobody
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Documentation        |                  Version:  1.10
     Severity:  Normal               |               Resolution:
     Keywords:  postgres unaccent    |             Triage Stage:
  trigram                            |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0

Comment (by Maxime Lorant):

 Replying to [comment:1 Tim Graham]:
 > It's not entirely clear to me why you want the instructions repeated
 twice, once at the top of the page and once within the docs for each
 extension -- or did I misunderstand the suggestion? Another consideration
 is that future lookups might not require activation of an extension.
 I don't think it should be write twice, but I guess it would not hurt if
 the usefulness of these two classes was more explicit so it can be easier
 to find it.

 (It is marked as cleanup, we can live with the current wording, but I
 think it could be better :) )

Ticket URL: <https://code.djangoproject.com/ticket/27355#comment:2>
Django <https://code.djangoproject.com/>
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 
For more options, visit https://groups.google.com/d/optout.

Reply via email to