Changes between Initial Version and Version 1 of Ticket #5219


Ignore:
Timestamp:
08/21/07 01:36:37 (8 years ago)
Author:
mtredinnick
Comment:

(Fixed wiki formatting in description.)

The modified table name is nothing to worry about. There's a maximum length on table names in Oracle, so we truncate them and a unique hash to the end.

The other bit (ignore null=False) is something I'll let the Oracle maintainers worry about.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5219

    • Property Patch needs improvement unset
    • Property Triage Stage changed from Unreviewed to Accepted
    • Property Needs tests unset
    • Property Needs documentation unset
  • Ticket #5219 – Description

    initial v1  
    22
    33When syncdbing the following model :
    4 
     4{{{
     5#!python
    56class IdentificationConfidence(models.Model):
    67       
     
    1213        def __unicode__(self):
    1314                return self.identification_confidence
    14 
     15}}}
    1516I get the following table produced:
     17{{{
    1618INTERACTION_IDENTIFICATION8A86
    17 
     19}}}
    1820with fields ID (PK) and
     21{{{
    1922IDENTIFICATION_CONFIDENCE NVARCHAR2(20) Nullable = Yes
    20 
     23}}}
    2124Syncdb seems to be ignoring null = false and providing a strange table name
    2225
     
    2528Catriona
    2629
    27 NB I didn't type the the question marks into my issue - they just appeared and it was __unicode__
     30NB I didn't type the the question marks into my issue - they just appeared and it was {{{__unicode__}}}
Back to Top