Opened 18 years ago

Closed 17 years ago

#313 closed defect (fixed)

Error handling in import plugins

Reported by: Johan Enell Owned by: Nicklas Nordborg
Priority: minor Milestone: BASE 2.1
Component: coreplugins Version: trunk
Keywords: Cc:


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)

comment:1 by Nicklas Nordborg, 18 years ago

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.

comment:2 by Jari Häkkinen, 18 years ago

Milestone: BASE 2.x+BASE 2.1

comment:3 by Nicklas Nordborg, 18 years ago

Priority: trivialmajor

comment:4 by Jari Häkkinen, 17 years ago

Milestone: BASE 2.1BASE 2.2
Summary: ReporterImporter cant handle to long stringReporterImporter cant handle too long string

comment:5 by Nicklas Nordborg, 17 years ago

Milestone: BASE 2.2BASE 2.1
Owner: changed from Johan Enell to Nicklas Nordborg
Priority: majorminor
Status: newassigned
Summary: ReporterImporter cant handle too long stringError handling in import plugins

comment:6 by Nicklas Nordborg, 17 years ago

Resolution: fixed
Status: assignedclosed

(In [2751]) Fixes #313: Error handling in import plugins

Note: See TracTickets for help on using tickets.