I've added a half-patch to ticket 683. I don't understand all the
magick going down in meta and models, but I hope the bit I did was
useful.
On 10/22/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> What you need to do is make sure the driver typecasts datetime
> database fields to Python datetime.date objects, and date database
> fields to Python datetime.date objects. Some database drivers do this
> automatically, but others provid
On 10/22/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> What you need to do is make sure the driver typecasts datetime
> database fields to Python datetime.date objects, and date database
> fields to Python datetime.date objects. Some database drivers do this
> automatically, but others provide
On 10/22/05, Jakub Labath <[EMAIL PROTECTED]> wrote:
> my model in dateapp is
> # Create your models here.
> class MyDate(meta.Model):
> day=meta.DateField()
>
> now follows the session from python interpreter
>
> >>> from django.models.dateapp import mydates
> >>> d = mydates.MyDate(day=datet
Hi
>
> But DateTime objects can be used to represent both; you just have a
> DateTime object with no time values.
Yes true, but it creates an error when running unittests, and I'm
assuming the tests are in place for a reason.
Best
jakub
# oops
# I put in date and I get datetime back.
But DateTime objects can be used to represent both; you just have a
DateTime object with no time values.
--
Jonathan Daugherty
http://www.parsed.org
