Changes between Initial Version and Version 1 of Ticket #16645, comment 6


Ignore:
Timestamp:
Sep 4, 2011, 6:04:34 PM (13 years ago)
Author:
Ramiro Morales

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #16645, comment 6

    initial v1  
    332011-08-28 15:36:35 <cramm> about the test failure with Oracle 11 related to a nullable filefield
    442011-08-28 15:37:18 <cramm> I've been reviewing it. I don't feel comfortable with adapting the tests to workaround that
    5 2011-08-28 15:38:37 <cramm> I konw there is some recommendation in the charfield docs discouraging using null=True, but we have a handful of models with FileField's and ImageField with null=tru in out tests, and they work correctly
     52011-08-28 15:38:37 <cramm> I know there is some recommendation in the charfield docs discouraging using null=True, but we have a handful of models containing FileField's and ImageField's with null=True in out tests, and they work correctly
    662011-08-28 15:39:57 <cramm> ... and a bunch of models with other CharField-derived fields also with null=True. In some tests we even test for ORM behavior when confronted with the null=Tree
    772011-08-28 15:40:42 <mYk> cramm: the problem here is that we test that an ImageField with no value has its name set to ''
    8 2011-08-28 15:40:47 <cramm> So, I'd prefer to see first why things don't fail in 10g and fail in 11g
     82011-08-28 15:40:47 <cramm> So, I'd prefer to see first why things don't fail in Oracle 10g and fail in 11g
    992011-08-28 15:41:03 <mYk> but since the field is nullable the result should be None
    10102011-08-28 15:41:47 <mYk> the docs don't say exactly how <file>.name is supposed to behave, but basically, it's the string stored in the db
Back to Top