Hi,
I see two solutions:
- be strict: Update the table to contain three columns.
day (0..6), start_hour and end_hour.
--> No need for MultiWidget
- don't be strict: Leave it as a charfield. I guess this field is
only read be humans. This gives you more possibilities:
Mon 15-17. Except in August 15-16.
if you can convert all current charfields to three columns (strict
solution),
I would take the first solution. If you can't since there are already
entries like the one above, choose the second.
BTW, my TimeDeltaField contains a widget which renders as several
input fields. Maybe it helps you:
http://www.djangosnippets.org/snippets/1060/
Thomas
mondonauta schrieb:
> thanks for the answer... anyway, my problem is that i already
> have a database so i don't really want to change it.
> in this case in particular i have a table called 'teachings'
> (that should be managed by the model i created)
> where all the subjects taught by a professor r stored.
> for each subject (in the teachings table) a single varchar field
> is used to store both a day and a time range to indicate when
> students can go to talk with the professor about that subject.
> so, i think it would be more user friendly to have 3
> choicefields: the first one for the day of the week,
> the second one for the "from time" field and the last one
> for the "to time" field.
>
--
Thomas Guettler, http://www.thomas-guettler.de/
E-Mail: guettli (*) thomas-guettler + de
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
