Re: [Django] #21699: Provide a way to define a model without being registered into the app registry / Get rid of get_registered_model

2024-03-12 Thread Django 
#21699: Provide a way to define a model without being registered into the app
registry / Get rid of get_registered_model
--+-
 Reporter:  Mitar |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e316382b6-0d306f0b-d61a-4327-a92c-f1cbc2e9aa4d-00%40eu-central-1.amazonses.com.

Re: [Django] #21699: Provide a way to define a model without being registered into the app registry / Get rid of get_registered_model

2021-12-16 Thread Django 
#21699: Provide a way to define a model without being registered into the app
registry / Get rid of get_registered_model
--+-
 Reporter:  Mitar |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by John Cronan):

 Hi! This is a very old ticket, but I've tested this same approach in 3.2
 and it still works. I'm doing a form-builder type of app, and I decided to
 use dynamic models.

 I get the warning message about "reloading models is not advised as it can
 lead to inconsistencies." In my case, I've ensured that the dynamic models
 don't use any foreign keys (except between each other).

 Considering the scope, "figure out what the registration API becomes":
 just as someone using this capability, I'd suggest that there could be a
 way to suppress the warning when you know that the side effects are not
 harmful. True unregistering, where the side effects with related models
 and such are removed automatically, would be cool but sounds hard.

-- 
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/063.5a6558dbf3d6bd32216e6bc83e02fb66%40djangoproject.com.

Re: [Django] #21699: Provide a way to define a model without being registered into the app registry / Get rid of get_registered_model

2015-02-09 Thread Django 
#21699: Provide a way to define a model without being registered into the app
registry / Get rid of get_registered_model
--+-
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by aaugustin):

 Yes. If you have multiple variants of a model with relations to another
 model, the reverse relations conflict on the other model.

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

Re: [Django] #21699: Provide a way to define a model without being registered into the app registry / Get rid of get_registered_model

2014-10-10 Thread Django 
#21699: Provide a way to define a model without being registered into the app
registry / Get rid of get_registered_model
--+-
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by kostko):

 > mitar, how should relations (foreign keys, one to one, many to many)
 between such a model and other models behave?

 Do you see any specific problems here?

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

Re: [Django] #21699: Provide a way to define a model without being registered into the app registry / Get rid of get_registered_model (was: Provide a way to define a model without being registered int

2014-01-26 Thread Django 
#21699: Provide a way to define a model without being registered into the app
registry / Get rid of get_registered_model
--+-
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  app-loading   | Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by aaugustin):

 mitar, how should relations (foreign keys, one to one, many to many)
 between such a model and other models behave?

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