#33797: Reword session docs on prioritizing "cache" vs "cached_db"
-------------------------------------+-------------------------------------
     Reporter:  Adam Johnson         |                    Owner:  Joseph V
         Type:                       |  Zammit
  Cleanup/optimization               |                   Status:  closed
    Component:  contrib.sessions     |                  Version:  dev
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"d959d66fa9b930c7264cb7db90e8ec626e2c44dd" d959d66f]:
 {{{
 #!CommitTicketReference repository=""
 revision="d959d66fa9b930c7264cb7db90e8ec626e2c44dd"
 [4.1.x] Fixed #33797 -- Prioritized cached database backend for cached
 sessions in docs.

 Co-authored-by: Adam Johnson <m...@adamj.eu>
 Backport of fa9ac16c1345a7fb6ad500c84961a954529ba2b9 from main
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33797#comment:7>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070183b163c258-5581a315-d7c5-427d-8405-d5539ca63a02-000000%40eu-central-1.amazonses.com.

Reply via email to