Home Original page

try pattern for database connection with the close method

Ian Kelly ian.g.kelly at gmail.com
Sat Feb 21 10:50:08 EST 2015 
On Sat, Feb 21, 2015 at 8:27 AM, Peter Otten <__peter__ at web.de> wrote:
> Ian Kelly wrote:
>
>> On Sat, Feb 21, 2015 at 5:22 AM, Mark Lawrence <breamoreboy at yahoo.co.uk>
>> wrote:
>>> try:
>>>     with lite.connect('data.db') as db:
>>>     try:
>>>         db.execute(sql, parms)
>>>     except lite.IntegrityError:
>>>         raise ValueError('invalid data')
>>> except lite.DatabaseError:
>>>     raise OSError('database file corrupt or not found.')
>>
>> This could result in the OSError being misleadingly raised due to some
>> DatabaseError raised by the execute rather than the connect.
>
> The OP probably wants to catch these DatabaseErrors, too. Also, the chance
> of a misleading traceback has been greatly reduced with the advent of
> chained exceptions.
>

Yes, but the point is that OSError is probably inappropriate in that case.
More information about the Python-list mailing list