Project

General

Profile

Evolution #3491

More visibility for fixture insertion error

Added by Gregg C. almost 6 years ago. Updated over 5 years ago.

Status:
Fermé
Priority:
Normal
Assignee:
Category:
ORM
Target version:
Start date:
12/20/2013
Due date:
% Done:

100%

Estimated time:
Bdc:

Description

Either :

- Throw RuntimeException when insertion error (application crash with stacktrace)
- Sub-transaction in fixture insertion (application won't crash and db will exist but will be empty)
- Try/catch the extractItem method (which is the method that will throw a RuntimeException if there are yaml errors in an Entity)
- Try/catch the getModelFixtures method (which is the method that will throw a RuntimeException if there are yaml errors in a fixture file (more globally))


Recurrences

History

#1Updated by Gregg C. almost 6 years ago

For now =>

extractItem try catched with more details on the problem (filename, problematic field, etc.)
no more try catch on ProviderInitialization as if it fails, the application cannot run anyway

#4Updated by CI-Build . almost 6 years ago

Build 501 finished UNSTABLE from merge request !1367

#5Updated by CI-Build . almost 6 years ago

Build 503 finished SUCCESS from merge request !1367

#6Updated by CI-Build . almost 6 years ago

Build 504 finished SUCCESS from merge request !1367

#8Updated by Gregg C. almost 6 years ago

What solution should I implement finally ? Is this one good enough ?

#10Updated by Mickael G. over 5 years ago

Check if ok (and the message)

Also available in: Atom PDF

Go to top
Add picture from clipboard (Maximum size: 200 MB)