Boris Pavlovic 69aaec2401 Refactor DB related exceptions
There is no need to create set of similar exceptions for every
record that we have in our database it actually makes life harder:

1) More code
2) More exceptions
3) More places to make mistake
4) Every time question to reuse exceptions or create new one
5) Handling of DB related exceptions becomes very hard

As well having single tree of exception related to DB makes handling easier:

- DBException (if you want to handle everything related to DB layer)
-- DBConlfict (conflicts with statuses)
-- DBRecrodNotFound (if record was not found)
-- DBRecrodExists (if unique constraints fails)

Deleted Exceptions:

- TaskNotFound(NotFoundException)
- DeploymentNotFound(NotFoundException)
- DeploymentNameExists(RallyException)
- DeploymentIsBusy(RallyException)
- ResourceNotFound(NotFoundException)
- TaskInvalidStatus(RallyException)

Change-Id: I98a91e05ffd48957767f837bcc24bc7341a7de25
2018-01-09 15:59:03 -08:00
..
2018-01-09 15:59:03 -08:00
2015-05-21 18:14:19 +03:00
2017-12-09 21:47:58 +00:00