Coming back to the topic. Will i be safe if i surround my SQL-related code with mySQLDb exceptions? As i understood that doing some tests that those are the exceptions raised by django.
Can anyone confirm this ? Or point me to another directions to handle SQL exceptions properly if there is some other way ? Thanks in advance Sebastien sebastien Pastor wrote: > Hi Simon, > > Thanks for your response! > I was more thinking of exceptions raised when something is terribly > wrong like mysql being down when you try to do a : > > Models.objects.all() > > > > or maybe also if you try to fetch data filtering with a filter with a > wrong data type. ... basically every exceptions that needs to be try: > ... except: ... to avoid the app to get screwed :) > > > Cheers > > Seb > > > [EMAIL PROTECTED] wrote: > >> Hi Seb :) >> >> There's no list of exceptions in the docs, but if other people think >> it's a good idea, I'll add it as a feature request. >> >> Anyway, Models.objects.all() will return an empty list ([]) if there's >> nothing in the database. Something like >> Model.objects.get(pk=somevalue) will raise a Models.DoesNotExist >> exception. Which other ones were you stuck on? >> >> --Simon >> >> >> >> >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
