Error handling in import plugins
The reporter importer (and pobably others) fails when there is to long strings in the input. BASE1 handels this by trimming the size to appropriate, is this the best solution?
Change History
(6)
| Milestone: |
BASE 2.x+ → BASE 2.1
|
| Priority: |
trivial → major
|
| Milestone: |
BASE 2.1 → BASE 2.2
|
| Summary: |
ReporterImporter cant handle to long string → ReporterImporter cant handle too long string
|
| Milestone: |
BASE 2.2 → BASE 2.1
|
| Owner: |
changed from Johan Enell to Nicklas Nordborg
|
| Priority: |
major → minor
|
| Status: |
new → assigned
|
| Summary: |
ReporterImporter cant handle too long string → Error handling in import plugins
|
| Resolution: |
→ fixed
|
| Status: |
assigned → closed
|
Maybe this should be configurable at the job level. Ie. the user could select one of three options: error, trim and skip. But this is not the only type of error that can happen. It should also be possible to configure what will happen in the case of: a required value is missing, a numeric value is outside the allowed range, etc. Possibly the AbstractFlatFileImporter could define parameters for those error handling options that are then easily included by the subclasses. Then, of course, it requires a bit of coding to make the plugins behave as the settings specify.