Basically, I have django create the table and the snippet from models.py is:
ExecutionStartDate = models.DateTimeField(verbose_name = "Start Date") And, then I have python load script which is loading the data with simple insert statements: The data in the input file is created = 22 Nov 2006 13:43:24.43 Through my django scripts it is truncating the .43. I would assume that if milliseconds is supported that I would have to specify it in my models.py definitions. Thanks, Jeff -------------- Original message -------------- From: "Jeremy Dunck" <[EMAIL PROTECTED]> > > On 3/27/07, Jonas Maurus wrote: > > > > On Mar 27, 7:58 pm, "jeffhg58" wrote: > .. > > > in the database. I am using a datetime field and when I insert the > > > record the milliseconds is being truncated. > > > > I find that strange, because Postgres doesn't natively support a > > column-type "datetime". Nevertheless, you can use a timestamp column > > for millisecond resolution > > He means Django's DateTimeField. > > Django creates a column of type 'timestamp with time zone' for > DateTimeField. The postgres docs claim microsecond resolution for > both with and without timezone. > > Can you share some code demonstrating the trouble? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
