Opened 18 years ago

Closed 17 years ago

#566 closed enhancement (fixed)

Plugins using the flat file parser should warn about complex column mappings

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: major Milestone: BASE 2.4
Component: coreplugins Version:
Keywords: Cc:

Description

Most mappings are from a single file column to a single data base column, ie. \Row\ The flat file parser allows combined mappings that can use multiple columns and/or constant strings in any combination, ie. \Row\,\Coloumn\

This kind of mapping is unusual and in three recent cases it was an error (an extra space or slash at the end of the column mapping).

By default, plugins should only allow the simple case and return an error message in the complex case. Then, a user may correct an incorrect mapping or use an extra parameter to specify if the complext mapping should be allowed or not.

See also ticket #563.

Change History (8)

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

Milestone: BASE 2.4BASE 2.3

Milestone BASE 2.4 deleted

comment:2 by Nicklas Nordborg, 17 years ago

Owner: changed from Johan Enell to Nicklas Nordborg
Status: newassigned

comment:3 by Nicklas Nordborg, 17 years ago

Resolution: fixed
Status: assignedclosed

(In [3493]) Fixes #566

comment:4 by Nicklas Nordborg, 17 years ago

Resolution: fixed
Status: closedreopened

The 'Complex column mapping' parameter is sneaking itself into the 'Column mappings' part of the 'Test with file' function. It is not a mapping expression and should not be visible there.

comment:5 by Nicklas Nordborg, 17 years ago

Status: reopenednew

comment:6 by Nicklas Nordborg, 17 years ago

Status: newassigned

comment:7 by Nicklas Nordborg, 17 years ago

The AnnotationFlatFileImporter doesn't check the column mappings as it should.

comment:8 by Nicklas Nordborg, 17 years ago

Resolution: fixed
Status: assignedclosed

(In [3598]) Fixes #566: Plugins using the flat file parser should warn about complex column mappings

Note: See TracTickets for help on using tickets.