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,
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
whats the folder structure for your templates?
On Sun, May 12, 2024 at 6:03 PM Yann wrote:
> Please does somoene can help me with this:
> [image: Capture d'écran 2024-05-12 091648.png]
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To
explain this with more context and snippets of code
On Mon, Apr 1, 2024 at 4:04 PM Moises Anibal
wrote:
> I can't for the life of me get my form data to pass from one view to
> another. I need help
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users
4 matches
Mail list logo
