Re: auto_now_add bug with MySQL

2006-05-29 Thread Jeroen Ruigrok van der Werven
On 5/29/06, Konstantin Shaposhnikov <[EMAIL PROTECTED]> wrote: > I've seen it here http://code.djangoproject.com/ticket/1056 (see the > first comment by jacob) > Though I am not sure how actual this statement is. Ticket seems to be quite > old. Luke fixed the code in the meantime though. It will

Re: auto_now_add bug with MySQL

2006-05-29 Thread Konstantin Shaposhnikov
On 5/29/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote: > Hi Konstantin, > > On 5/29/06, Konstantin Shaposhnikov <[EMAIL PROTECTED]> wrote: > > I suggest you to not use auto_now_add at all if you are using current > > (post magic-removal) version of django. > > I am using the SVN trunk

Re: auto_now_add bug with MySQL

2006-05-29 Thread Petar Marić
auto_now_add has been fixed in [3002] Hurray for Luke ;) -- Petar Marić *e-mail: [EMAIL PROTECTED] *mobile: +381 (64) 6122467 *icq: 224720322 *skype: petar_maric *web: http://www.petarmaric.com/ --~--~-~--~~~---~--~~ You received this message because you are subs

Re: auto_now_add bug with MySQL

2006-05-29 Thread Jeroen Ruigrok van der Werven
Hi Konstantin, On 5/29/06, Konstantin Shaposhnikov <[EMAIL PROTECTED]> wrote: > I suggest you to not use auto_now_add at all if you are using current > (post magic-removal) version of django. I am using the SVN trunk yes. (It would be great if someone could finally fix trunk's setup.py to reflect

Re: auto_now_add bug with MySQL

2006-05-29 Thread Konstantin Shaposhnikov
Hello, On 5/29/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote: > Andy, > > On 5/8/06, Andy Dustman <[EMAIL PROTECTED]> wrote: > > Try the patch on this bug: > > The 2nd patch didn't work for me, as I noted in the ticket. > > The initial save with DateField(auto_now_add = True) is corr

Re: auto_now_add bug with MySQL

2006-05-29 Thread Jeroen Ruigrok van der Werven
Andy, On 5/8/06, Andy Dustman <[EMAIL PROTECTED]> wrote: > Try the patch on this bug: The 2nd patch didn't work for me, as I noted in the ticket. The initial save with DateField(auto_now_add = True) is correct, it has the date as it should. But using it in conjunction with FileField() will cause

Re: auto_now_add bug with MySQL

2006-05-08 Thread Andy Dustman
On 5/5/06, Petar Mariæ <[EMAIL PROTECTED]> wrote: > class Paper(models.Model): > # ... > submited_on = models.DateField( > auto_now_add=True, > ) > # ... > > The above will spit out: > Exception Type: ValueError > Exception Value:year is out of range > Except

Re: auto_now_add bug with MySQL

2006-05-06 Thread Petar Marić
Fernando, It looks it's my own fault I failed to mention I was adding a new object via Djangos admin interface. That means it's Djangos fault, not mine ;) -- Petar Marić *e-mail: [EMAIL PROTECTED] *mobile: +381 (64) 6122467 *icq: 224720322 *skype: petar_maric *web: http://www.petarmaric.com/ --

Re: auto_now_add bug with MySQL

2006-05-05 Thread Fernando Gutierrez Honorio
Petar, how was your object added? I had that problem when using the create function and save, for example using the model: class B(models.Model): date = models.DateField(auto_now_add=True) a = models.ForeignKey(A) doing this considering "object" is an object of class A, this produces

auto_now_add bug with MySQL

2006-05-05 Thread Petar Marić
class Paper(models.Model): # ... submited_on = models.DateField( auto_now_add=True, ) # ... The above will spit out: Exception Type: ValueError Exception Value:year is out of range Exception Location: C:\Dev\Python24\lib\site-packages\MySQLdb\connect