#11015: django-1.0.2 does not catch the exception that database backend first 
close
the db connection.
---------------------------------------------------+------------------------
          Reporter:  qingran                       |         Owner:  nobody
            Status:  closed                        |     Milestone:        
         Component:  Database layer (models, ORM)  |       Version:  1.0   
        Resolution:  worksforme                    |      Keywords:        
             Stage:  Unreviewed                    |     Has_patch:  0     
        Needs_docs:  0                             |   Needs_tests:  0     
Needs_better_patch:  0                             |  
---------------------------------------------------+------------------------
Comment (by russellm):

 Replying to [comment:6 gkulewski]:
 > That was really helpful, thanks.
 >
 > Good it works for you. But it does not work for others. Look above. Use
 google to get many more such results. Something definitively _is_ broken,
 it's just hard to track it down.

 If this were a serious or regularly occurring problem, I wouldn't need to
 use Google. It would be a regular topic on Django-users, django-dev, or an
 observable issue on any one of the *many* Django sites that I and the rest
 of the core team manage personally. Neither of these things are true.

 > I will post if I have more info.

 Which is exactly what I asked you to do.

 Please consider this from our point of view. We have a report of a fairly
 generic sounding error, that can apparently be generated under unknown
 conditions. I can't reproduce the error myself. There has been no evidence
 presented that this is anything other than a cosmetic problem (ok - sure,
 there is an error message, but does that mean data is being lost, or just
 that it's an annoying log entry?). I can't even be certain that this isn't
 due to a misconfiguration of the servers in question -- for example, if
 your database server has a timeout set much shorter than your web server's
 page delivery timeout, for example.

 As I said - If someone is able to provide instructions for reproducing
 this bug -- even if only intermittently or on specific setups -- I'm only
 to happy to investigate further. However, there is literally *nothing* we
 can do until you can tell us how to reproduce the problem.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/11015#comment:7>
Django <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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to