* drop workaround for application crash on WinXP, when loading newer libmariadb (see #79)
* raise TDbLib's own exception instead of baking an own one with less details. Probably helps in debugging: https://www.heidisql.com/forum.php?t=34044
* rename EDatabaseError to EDbError, to overcome naming conflict in DB unit
* load libpq.dll always with path, which should anyway work better than without it. See http://www.heidisql.com/forum.php?t=22514
This commit is contained in:
Ansgar Becker
2019-07-08 20:23:05 +02:00
parent 4f9613b05c
commit 2a91a13b42
18 changed files with 162 additions and 185 deletions

View File

@ -621,7 +621,7 @@ var
tmBulkTableEdit: DoBulkTableEdit(DBObj);
end;
except
on E:EDatabaseError do begin
on E:EDbError do begin
// The above SQL can easily throw an exception, e.g. if a table is corrupted.
// In such cases we create a dummy row, including the error message
AddNotes(DBObj, 'error', E.Message);
@ -1233,7 +1233,7 @@ begin
comboExportOutputTarget.ItemIndex := 0;
Screen.Cursor := crDefault;
except
on E:EDatabaseError do begin
on E:EDbError do begin
Screen.Cursor := crDefault;
ErrorDialog(E.Message);
comboExportOutputType.ItemIndex := FLastOutputSelectedIndex;
@ -1629,7 +1629,7 @@ begin
Output(Struc, True, True, True, True, True);
Output(CRLF, False, True, True, True, True);
except
on E:EDatabaseError do begin
on E:EDbError do begin
// Catch the exception message and dump it into the export file for debugging reasons
Output('/* '+E.Message+' */', False, True, True, False, False);
Raise;