#5929: Allow Fields to use multiple db columns (complex datatypes)
-------------------------------------+-------------------------------------
     Reporter:  Daniel               |                    Owner:  HAMA
  Poelzleithner                      |  Barhamou
         Type:  New feature          |                   Status:  closed
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  duplicate
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by HAMA Barhamou):

 I agree with Simon on clarifying the issue and defining a clear interface
 before pursuing composite field implementation. Here are some concrete
 proposals:

 Let's define a minimal prototype for composite primary keys using existing
 fields as arguments.
 We can then gradually expand to other use cases.
 It would be useful to gather concrete examples of users who would need
 composite fields before starting development.
 Although my schedule has been busy lately and my level with Django is
 limited, I'm open to exploring this idea.

 Replying to [comment:36 Csirmaz Bendegúz]:
 > Replying to [comment:35 Simon Charette]:
 >
 > That makes sense, thanks Simon! You're right about the `output_field`
 use case.
 >
 > Generalizing `CompositePrimaryKey` -> `CompositeField` should be a
 straightforward task I think. `CompositeField` could accept fields as
 arguments (not only field names).
 >
 > HAMA Barhamou maybe you would like to work on this?
-- 
Ticket URL: <https://code.djangoproject.com/ticket/5929#comment:38>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/01070193ab35a44b-fdc4ad39-1645-41cb-97ba-3e7e05b1bed8-000000%40eu-central-1.amazonses.com.

Reply via email to