Hi,
I ended up creating a custom field (
https://github.com/clearspark/django-monthfield).
I used a lot of your input, thank you all.
Cheers,
Matthys
On Mon, May 4, 2015 at 7:09 PM, Tim Chase
wrote:
> On 2015-05-03 14:35, Matthys wrote:
> > I posted the question also on stackoverflow:
> >
>
Hi Erik,
Thanks for your reply.
I'm aware of the problems with timedelta(months=2), since the length of a
month is not fixed, a length of time specified in months is ambiguous.
Though months do have an internally consistent algebra as you point out and
people often refer to time-periods in month
Hi,
I'm specifically looking at only situations where the year and month alone
are significant.
The downside I see with using a DateField and forcing the day to the first
of the month, with custom widget etc. is that somebody looking at the
database may not realize that something unusual is going
django validators in non-django
projects. It is obviously possible to code around this but I am curious as
why it was done like this and what others have done to get around this.
Kind regards,
Matthys Kroon
--
You received this message because you are subscribed to the Google Groups
4 matches
Mail list logo