Re: ticket 5929

2023-01-10 Thread Barhamou Hama
Hi, I'm glad I contributed to something. I understand your point of view. I'm new and looking for an interesting topic to work on in my spare time. I don't want to waste my energy on a feature that doesn't get a lot of support. However, if this ticket still exists, there must be a problem somewh

Re: ticket 5929

2023-01-10 Thread 'Tobias McNulty' via Django developers (Contributions to Django itself)
Thank you Barhamou for raising the question here and starting the discussion. I agree with Adrian that this feels like a pretty niche use case. Depending on the needs, other possible implementations might include: 4. A form field mapping to multiple model fields 5. A custom queryset/manager that

Re: ticket 5929

2023-01-09 Thread Barhamou Hama
Hence the interest of my question, if in 15 years it has not been solved, there must be a reason. Le lundi 9 janvier 2023 à 12:57:31 UTC+1, ator...@redhat.com a écrit : > I feel like this is a very niche use case and probably doesn't warrant > implementing field-to-column one-to-many relationsh

Re: ticket 5929

2023-01-09 Thread Barhamou Hama
Thanks, I will study the question to find out more. Le lundi 9 janvier 2023 à 00:16:56 UTC+1, cur...@tinbrain.net a écrit : > On Sun, 8 Jan 2023, at 23:29, Barhamou Hama wrote: > > Hi all, I came across this ticket here > opened 15 years ago that > d

Re: ticket 5929

2023-01-09 Thread Adrian Torres
I feel like this is a very niche use case and probably doesn't warrant implementing field-to-column one-to-many relationships in Django, I don't see why this specific case can't be implemented as: 1. A model that implements the data type 2. A custom field + custom datatype on the database backen

Re: ticket 5929

2023-01-08 Thread Curtis Maloney
On Sun, 8 Jan 2023, at 23:29, Barhamou Hama wrote: > Hi all, I came across this ticket here > opened 15 years ago that doesn't > seem to have been resolved. I decided to work on it. But in 15 years a lot > can happen. Is it still relevant? Has there b