#4193: Error in creation of foreign key depends on spelling of field class
-----------------------------------------------+----------------------------
   Reporter:  [EMAIL PROTECTED]                 |                Owner:  adrian 
         
     Status:  new                              |            Component:  
Database wrapper
    Version:  SVN                              |           Resolution:          
        
   Keywords:  foreignKey, spelling, SQL error  |                Stage:  
Unreviewed      
  Has_patch:  0                                |           Needs_docs:  0       
        
Needs_tests:  0                                |   Needs_better_patch:  0       
        
-----------------------------------------------+----------------------------
Comment (by anonymous):

 Replying to [comment:2 SmileyChris]:
 > Thanks for the report, Gerry - weird sounding bug...
 >
 > I know it's asking a lot, but do you think you could make a model test
 for this?
 
 I started looking into this yesterday, but got distracted by my real(TM)
 job.   :)
 I'll give it a try, but my effort will be sporadic.
 
 I dug through the django documentation and found this page:
 
    [http://www.djangoproject.com/documentation/testing/]
 
 By "model test" I assume building a doctest string in the models.py file.
 I've thought about it, but I haven't gotten any traction on how to test
 that the correct SQL was created.  Any suggestions on that front are
 welcome.
 
 Gerry

-- 
Ticket URL: <http://code.djangoproject.com/ticket/4193#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to