Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:
 |  AllenJonathan
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  GSoC | 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:"be6a309b1d749c47821dfdc5add6576f2c61cda0" be6a309]:
 {{{
 #!CommitTicketReference repository=""
 revision="be6a309b1d749c47821dfdc5add6576f2c61cda0"
 [4.2.x] Refs #29799 -- Added field instance lookups to suggestions in
 FieldErrors.

 Bug in cd1afd553f9c175ebccfc0f50e72b43b9604bd97.
 Backport of 3afdc9e9b47d5bdd1bd653633b4cb2357478ade5 from main
 }}}

-- 
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/01070187293bede0-d1d552fd-3914-4187-943e-f9eeaa8fab51-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:
 |  AllenJonathan
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  GSoC | 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 GitHub ):

 In [changeset:"3afdc9e9b47d5bdd1bd653633b4cb2357478ade5" 3afdc9e9]:
 {{{
 #!CommitTicketReference repository=""
 revision="3afdc9e9b47d5bdd1bd653633b4cb2357478ade5"
 Refs #29799 -- Added field instance lookups to suggestions in FieldErrors.

 Bug in cd1afd553f9c175ebccfc0f50e72b43b9604bd97.
 }}}

-- 
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/01070187293b7644-b792e579-9a59-4340-9bda-97202a486d8c-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:
 |  AllenJonathan
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  GSoC | 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:

 See
 
https://github.com/django/django/commit/cd1afd553f9c175ebccfc0f50e72b43b9604bd97.

-- 
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/01070182fdca6f37-6a70ceee-11c8-41ee-bbfe-dc7a4280c54d-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:
 |  AllenJonathan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  GSoC | 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):

 * stage:  Accepted => Ready for checkin


-- 
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/01070182fd3a0bd2-4be04f23-3841-4dbe-a82e-459ed8d4bdc0-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:
 |  AllenJonathan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  GSoC | 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 ):

 In [changeset:"e64919ae54933ef4840f0e27e51d9fcfd55ecf4b" e64919ae]:
 {{{
 #!CommitTicketReference repository=""
 revision="e64919ae54933ef4840f0e27e51d9fcfd55ecf4b"
 Refs #29799 -- Added more tests for registering lookups.
 }}}

-- 
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/01070182f835dafa-d7102405-23d8-4ca5-b288-a9423ee891ce-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:
 |  AllenJonathan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  GSoC | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/15787 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/01070182f7de442b-a325be4a-fcc4-43fc-8709-3570c33e8059-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:
 |  AllenJonathan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  GSoC | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * cc: Simon Charette (added)
 * needs_better_patch:  1 => 0
 * owner:  Can Sarıgöl => AllenJonathan
 * keywords:   => GSoC
 * needs_docs:  1 => 0
 * has_patch:  1 => 0


-- 
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/01070180f4b77410-2302b1f8-3c02-4d48-9690-70d27930172e-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:  Can
 |  Sarıgöl
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Himanshu Balasamanta):

 * cc: Himanshu Balasamanta (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/0107018064f8a8dd-1228abec-56d0-4c32-89ab-e566541662a6-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:  Can
 |  Sarıgöl
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Himanshu Balasamanta):

 Replying to [comment:8 Carlton Gibson]:

 > The rough outline looks right. There are various variations but, ''I'd
 like to add a custom lookup just for **this** model'' — the model being
 the bearer of field instances; ''I'd like to disable **this** lookup on
 this model'', and so on.
 Agreed. It would be more user friendly.
 So, along with register_lookup(self,lookup,lookup_name), I shall add a
 Model.register_lookup(field_name : str, lookup : Lookup, lookup_name :
 str) too.

 > I know you're looking at this targeting GSoC, so for the the sake of a
 proposal, noting the areas to be decided is OK. Showing that you've
 considered points already raised is important — make sure you looked at
 [https://github.com/django/django/pull/15529#issuecomment-1073412321
 Simon's comment on your draft PR] — I'm sure you did. Plus #33626 and the
 PR there you've made are all good signs — that's on my list to review next
 week.
 >
 > I hope that helps. 
 >
 >
 Thank You!

-- 
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/0107018012db8594-dc5ec5cc-489f-4a45-9fbd-687947376144-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:  Can
 |  Sarıgöl
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Hi Himanshu.

 The rough outline looks right. There are various variations but, ''I'd
 like to add a custom lookup just for **this** model'' — the model being
 the bearer of field instances; ''I'd like to disable **this** lookup on
 this model'', and so on.

 The specific behaviours are hard to say definitively one way or the other
 until we get to the review stage. Looking at test cases, and seeing how
 the API looks at that point is much easier to speak clearly to.

 (For example, I'm not sure what to say about trying to unregister a non-
 registered lookup on a class... — we **could** error, or we could `pass`:
 the end effect is that the lookup is not registered on the class... 樂 —
 it's the kind of detail we can settle with multiple sets of eyes at review
 time.)

 I know you're looking at this targeting GSoC, so for the the sake of a
 proposal, noting the areas to be decided is OK. Showing that you've
 considered points already raised is important — make sure you looked at
 [https://github.com/django/django/pull/15529#issuecomment-1073412321
 Simon's comment on your draft PR] — I'm sure you did. Plus #33626 and the
 PR there you've made are all good signs — that's on my list to review next
 week.

 I hope that helps. 

-- 
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/010701800a9af916-8b73693a-958b-406a-afd9-0bd2b8970b75-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:  Can
 |  Sarıgöl
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sergey Fedoseev):

 * cc: Sergey Fedoseev (removed)


-- 
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/010701800a1e8cf3-4dff4df0-449a-4cd4-82a2-d2091184af6e-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:  Can
 |  Sarıgöl
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Himanshu Balasamanta):

 @carltongibson , @charettes . I wanted to clarify exactly what all the
 scope of the ticket covers.
 As per my understanding,
 - Enable registration and remove a lookup for a particular instance as
 opposed to a class.
 - Enable lookups registered for the class to be unregistered (and maybe
 re-registered?) for instances of that class.

 Description of the functions would be as follows

 - get_lookups()
   - when called by a field instance, returns all class and instance
 lookups currently registered for that field instance
   - when called by a class, returns all class lookups currently registered
 for that class

 - register_lookup
   - when called by a field instance, registers the lookup for that field
 instance
   - when called by a class, registers the lookup for that class

 - unregister_lookup
 1. when called by a field instance,
- if the lookup is already registered with the instance, it gets
 removed,
- if the lookup is registered with the instance class, that particular
 instance is exempted
- else throws error
 2. when called by a class, if the lookup is already registered with the
 class, it is removed. Else error is thrown.

 Doubts:
 1. Should class lookups that are unregistered for an instance be re-
 registered using the register_lookup method itself?
 2. Should there be a method to specifically get lookups that were
 registered for the instance and not the class?

-- 
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/0107018009eccbee-2ffcb701-19b9-4b05-8b6b-0747a2fb7740-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:  Can
 |  Sarıgöl
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

 * status:  new => assigned
 * owner:  nobody => Can Sarıgöl


-- 
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/067.2d67af3ef1ccb37ab2cb337725eff610%40djangoproject.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1
 * needs_docs:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.0a5f735242e2eafce66c95f1a70627c3%40djangoproject.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:  nobody
 Type:  New feature  |   Status:  new
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:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Can Sarıgöl):

 * cc: Can Sarıgöl (added)
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/11408 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 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/067.c0080109ef16110b75e0c249d0256993%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sergey Fedoseev):

 * cc: Sergey Fedoseev (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 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/067.25c680ce5708a8c873682b5d7b5fd0c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 Yes. Super.

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

[Django] #29799: Allow registration and unregistration of lookups per field instances.

[Django]

#29799: Allow registration and unregistration of lookups per field instances.
-+-
   Reporter:  Simon  |  Owner:  nobody
  Charette   |
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Under certain circumstances it might be useful to register or unregister
 model field lookups on a per instance basis instead of a per class basis.

 For example, it could be useful to disable costly lookups such as
 `contains` and `icontains` on some large table model `CharField`s without
 defining them using a `CharField` subclass to prevent them from being used
 in production. Similarly you might want to register or override a specific
 lookup for a third party app model field that doesn't allow swapping.

 This was initially mentioned in #16187 which introduced this new lookup
 registration system.

 https://code.djangoproject.com/ticket/16187#comment:14

 > Having the ability to hook a custom lookup to a given field instance
 would be really nice to have...

 https://code.djangoproject.com/ticket/16187#comment:22

 > Add a way to register lookups to fields (I think either instances or
 classes is wanted behaviour).

 But not discussed afterwhile. I believe class based registration was
 chosen because it was easier to implement but I agree that being able to
 register custom lookups per field instance would be good feature addition.

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