Re: ticket 5929

2023-01-10 Thread Barhamou Hama
ther possible implementations might include: > > 4. A form field mapping to multiple model fields > 5. A custom queryset/manager that takes "shorthand filter queries" and > expands them to multiple model fields > > As for the example in #5929 <https://code.djangop

Re: ticket 5929

2023-01-10 Thread 'Tobias McNulty' via Django developers (Contributions to Django itself)
takes "shorthand filter queries" and expands them to multiple model fields As for the example in #5929 <https://code.djangoproject.com/ticket/5929> ticket description, that is probably best solved with #2 on Adrian's list, for example the django-netfields <https://pypi.org/

Re: ticket 5929

2023-01-09 Thread Barhamou Hama
roject.com/en/4.1/ref/contrib/postgres/fields/#arrayfield > On Monday, January 9, 2023 at 12:16:56 AM UTC+1 cur...@tinbrain.net wrote: > >> On Sun, 8 Jan 2023, at 23:29, Barhamou Hama wrote: >> >> Hi all, I came across this ticket here >> <https://code.djangop

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 > <https://code.djangoproject.com/ticket/5929> opened

Re: ticket 5929

2023-01-09 Thread Adrian Torres
across this ticket here > <https://code.djangoproject.com/ticket/5929> 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 been any progress > on this issue? > > >

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 > <https://code.djangoproject.com/ticket/5929> 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 st

ticket 5929

2023-01-08 Thread Barhamou Hama
Hi all, I came across this ticket here <https://code.djangoproject.com/ticket/5929> 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 been any progress on this issue? -- You re

Re: [GSoC] Ticket #5929 (Previously Serialization Refactor)

2009-03-22 Thread Malcolm Tredinnick
On Sun, 2009-03-22 at 14:07 +0530, Madhusudan C.S wrote: [...] > > To be very frank I haven't myself come up with anything > concrete till now, since the ideas list themselves don't > tell anything in specific, but just give a hint to what > might be lead to a potential GSoC project. B

Re: [GSoC] Ticket #5929 (Previously Serialization Refactor)

2009-03-22 Thread Madhusudan C.S
Hi Malcolm, Thanks a lot for replying. On Sun, Mar 22, 2009 at 3:08 AM, Malcolm Tredinnick < malc...@pointy-stick.com> wrote: > > > Hi Malcolm and all, > > Doesn't ticket #5929 (http://code.djangoproject.com/ticket/5929) > > look very similar to what I prop

Re: [GSoC] Ticket #5929 (Previously Serialization Refactor)

2009-03-21 Thread Malcolm Tredinnick
On Sat, 2009-03-21 at 23:16 +0530, Madhusudan C.S wrote: > Hi Malcolm and all, >Doesn't ticket #5929 (http://code.djangoproject.com/ticket/5929) > look very similar to what I proposed for Python? Allowing Python > built in complex datatype objects to be mapped to Relational

[GSoC] Ticket #5929 (Previously Serialization Refactor)

2009-03-21 Thread Madhusudan C.S
Hi Malcolm and all, Doesn't ticket #5929 (http://code.djangoproject.com/ticket/5929) look very similar to what I proposed for Python? Allowing Python built in complex datatype objects to be mapped to Relational Database (which includes lists, dictionaries and tuples)? May be an addit