#4146: Database Module Conflicts
------------------------------------------------+---------------------------
   Reporter:  David Cramer <[EMAIL PROTECTED]>  |                Owner:  adrian 
         
     Status:  new                               |            Component:  
Database wrapper
    Version:  SVN                               |           Resolution:         
         
   Keywords:                                    |                Stage:  
Unreviewed      
  Has_patch:  0                                 |           Needs_docs:  0      
         
Needs_tests:  0                                 |   Needs_better_patch:  0      
         
------------------------------------------------+---------------------------
Comment (by mtredinnick):

 We really need a better bug report here. I have no idea what problem is
 being reported. That paste example doesn't explain a number of things, as
 well as exhibiting some bad practices that may not ever be able to work
 (doing a query on the !Equpiment class as the !Import class is being
 defined is dubious).
 
 Instead of asking us to reverse-engineer the problem from a fragment,
 please detail clearly:
  1. What is actually going wrong
  2. What you would expect to happen instead

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