#8316: MySQL error with custom primary_key that is not an IntegerField
---------------------------------------+------------------------------------
          Reporter:  julianb           |         Owner:  julianb
            Status:  new               |     Milestone:  1.0    
         Component:  Database wrapper  |       Version:  SVN    
        Resolution:                    |      Keywords:         
             Stage:  Accepted          |     Has_patch:  1      
        Needs_docs:  0                 |   Needs_tests:  1      
Needs_better_patch:  1                 |  
---------------------------------------+------------------------------------
Changes (by spaetz):

 * cc: [EMAIL PROTECTED] (added)

Comment:

 Ouch, got bitten by this today. Latest patch seems to have tests, can
 people look at it and reset the tests flag if appropriate?

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8316#comment:6>
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