Je suis disposé, crache le marché
Le mar. 4 févr. 2025, 15:25, Idohou Sandé Augustin a
écrit :
> I'm looking for back end developer Django
>
> Le mar. 4 févr. 2025, 06:03, Agar Joshua a
> écrit :
>
>> Hi I agree with alexei.ramo...@gmail.com renaming fields and doing
>> migrations is definitely
Mayank
I think you should not delete and add the fields rather make them one
consistent model so that while reporting or may be during data analytics
that will play big role since it’s just date field.
Otherwise changing the model may need migration which is like adding an
extra process
All the
I'm looking for back end developer Django
Le mar. 4 févr. 2025, 06:03, Agar Joshua a écrit :
> Hi I agree with alexei.ramo...@gmail.com renaming fields and doing
> migrations is definitely not the most optimal solution. I suggest you have
> generic names. Anything variable mostly ends up being a
Implémenter un processus de modification quotidienne des champs de modèle
dans un projet Django peut être complexe, mais c'est faisable. Voici
quelques points à considérer pour garantir que le processus fonctionne
efficacement dans un environnement de production :
✅Planification des tâches:
Pour a
Hi I agree with alexei.ramo...@gmail.com renaming fields and doing
migrations is definitely not the most optimal solution. I suggest you have
generic names. Anything variable mostly ends up being a field on a table or
a table, depending on your use case. I hope you figured that out though?
On Wed,
handling in Django
I am making train ticket booking project in which I have to keep record of
number of tickets booked and remaining seats for 60 days from today. So as the
day passes , passed date field have to be removed and new date after 59 days
from today has to be added.
On Wed, 29
I'd just give the columns generic names and let react handle the names you
want to display which is probably based on dates or something cyclical.
Otherwise it seems like too much overhead in renaming fields and migration.
On Wed, Jan 29, 2025, 2:56 PM 'Ryan Nowakowski' via Django users <
django-u
On 1/27/25 7:41 AM, Mayank Prajapati wrote:
> I am making a full stack project with JavaScript and react for front end ,
> Postgre SQL for database and Django for backend and Django rest framework for
> APIs. So in models.py file there's one field which is to be removed and
> another field is t
I am making train ticket booking project in which I have to keep record of
number of tickets booked and remaining seats for 60 days from today. So as
the day passes , passed date field have to be removed and new date after 59
days from today has to be added.
On Wed, 29 Jan 2025, 12:24 pm Agar Josh
This is an interesting implementation. I am curious, what are you trying to
achieve that necessitates adding and removing fields? And wouldnt that be
solved better with some table relationship instead?
On Tue, Jan 28, 2025 at 1:33 AM Mayank Prajapati <
mayankprajapati1...@gmail.com> wrote:
> I am
It will work normally, go ahead.
On Mon, Jan 27, 2025, 11:33 PM Mayank Prajapati <
mayankprajapati1...@gmail.com> wrote:
> I am making a full stack project with JavaScript and react for front end ,
> Postgre SQL for database and Django for backend and Django rest framework
> for APIs. So in model
I am making a full stack project with JavaScript and react for front end ,
Postgre SQL for database and Django for backend and Django rest framework
for APIs. So in models.py file there's one field which is to be removed and
another field is to be added at the end. This process has to be done on
12 matches
Mail list logo
