Thank you very much Kenneth. I think this is a one-off error for now. If I face to this problem again I'll use default=datetime.now. But I couldn't understand why this happens? Who causes this problem django middleware or oracle db? Which one supposed to achieve this auto add action?
2011/5/16 Kenneth Gonsalves <law...@thenilgiris.com> > On Mon, 2011-05-16 at 13:43 +0300, Burcu Hamamcıoğlu wrote: > > ORACLE. > > long ago I used to have a lot of errors where there was an auto_now_add > field along with an image/file field in the same model. At one time > auto_now_add was deprecated and we were advised to use > default=datetime.now. If this is not a one-off error, you may look at > this work around. > -- > regards > KG > http://lawgon.livejournal.com > Coimbatore LUG rox > http://ilugcbe.techstud.org/ > > -- > 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 > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
