search

vatplanner / importer-status-postgis

VATPlanner Status Importer to PostGIS
MIT License
0 stars 0 forks source link

do not save overlong field data #4

Open dneuge opened 3 years ago

dneuge commented 3 years ago

Callsigns in general are supposed to be rather short. From time to time something else gets submitted in the callsign field which breaks any limit previously set up on the flights database table resulting in an SQL error aborting the data import.

It would be better to check the callsign length for violations and block avoid submitting such data. Callsigns cannot be cut short as they identify flights and they cannot be aliased without another storage due to restarting imports. The only option seems to be to not save such flights at all.

dneuge commented 3 years ago

The issue is unfortunately not limited to just one field, it appears that the new prefiling form now allows data of practically any length to other fields as well. Seen on aircraft type as well.