[Django] #27589: SearchVectorField with built-in managed triggers

[Django]

#27589: SearchVectorField with built-in managed triggers
-+-
   Reporter:  Lex|  Owner:  (none)
  Berezhny   |
   Type:  New| Status:  assigned
  feature|
  Component: |Version:  master
  contrib.postgres   |   Keywords:  fts search
   Severity:  Normal |  postgresql
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 This is a significantly enhanced version of
 django.contrib.postgresql.search.SearchVectorField with automatically
 generated and managed database trigger.

 https://github.com/django/django/pull/7678

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

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

[Django]

#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Andrey
 Type:   |  Kuzminov
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Ian Foote):

 * needs_better_patch:  0 => 1


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

Re: [Django] #20456: Easier unit testing for class-based views

[Django]

#20456: Easier unit testing for class-based views
---+
 Reporter:  Benoît Bryon   |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  cbv test   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham):

 * status:  assigned => new
 * owner:  Marc Tamlyn => (none)


Comment:

 I don't see anyone actively working on it. Feel free to work on it if you
 like.

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