Hi everyone,
Would it be possible to provide a new inheritance mechanism between classes
in Django ?
I explain my point :
I have an app, for instance "HR": In this app, I would manage a model that
is called "Employee". I store several information on this model and it's
fine.
Suppose I have a
I think this is more of a django-users comment, so I'll post Adam's
template for places.
I think you've found the wrong mailing list for this post. This mailing
list is for the development of Django itself, not for support using Django.
This means the discussions of bugs and features in Django its
Hi all.
>From GSoC last year, Sage has a CrossDB JSONField for us:
https://github.com/django/django/pull/12392
We still have a bit more close review to do but...
*We need people to give it an outing, to find issues/regressions and so
on. *
PostgreSQL:
Clone your DB etc. Change your P
No this is not a django-user-code related post. The code I provided was
only an example to illustrate the feature request.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and
How would the fields in HRFleetEmployee be persistent and linked to a
particular Employee or Vehicle without being saved in the database? Or did
I understand your code and request wrong?
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributio
I've never said it isn't saved in database. It is saved but in the table of
the employee since hrfleetemployee inherits from employee. It simply adds
this field to the table of Employee
Le jeu. 30 janv. 2020 à 5:24 PM, Abhijeet Viswa a
écrit :
> How would the fields in HRFleetEmployee be persist
I think this would needlessly complicate the entire migration process. Two
different app migrations (and possibly even more) would have be considered
and executed in sequence to prevent anything breaking on the database.
On Thu, 30 Jan 2020 at 22:00, LBris wrote:
> I've never said it isn't saved
I do not understand. Could you explain to me what it would break the
database and how ?
Le jeudi 30 janvier 2020 17:37:22 UTC+1, Abhijeet Viswa a écrit :
>
> I think this would needlessly complicate the entire migration process. Two
> different app migrations (and possibly even more) would have
Each model represents one table on the DB. Modifying it in two different
apps (hence creating two different sets of migrations) might result in
breaking changes. What if one migration affects something that is directly
referenced by the other app, but wasn't updated?
Also, what would the potential
