(and
> relies upon) this backward relation to the Vehicle model (and hence the 2nd
> app itself).
>
> On Thu, 30 Jan 2020 at 23:07, LBris >
> wrote:
>
>> I do not understand. Could you explain to me what it would break the
>> database and how ?
>>
>>
ould 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 in database. It is saved but in the table
>> of the employee since
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
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
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
>
> Hi everyone.
What is the state of this discussion and its attached ticket ?
--
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 stop receiving emails from it, send an e
Yes I saw this ticket before requesting the feature but I don't know at
which state this ticket is (is it in progress ? do they need help ? Will it
be even possible ? Will it be done and integrated to Django ?)
I'm aware with other solutions such as doing a OneToOne relation but in my
opinion
Hi everyone.
As it is possible to customize the User model using AbstractUser or
AbstractBaseUser, it would be great to be able to do the same with groups
and permissions.
The goal is to provide 2 new abstract models "AbstractGroup" and
"AbstractPermission", in order to benefit from all the al
