Opened 12 years ago
Closed 12 years ago
#2270 closed enhancement (wontfix)
Set NOT NULL constraint on the geometry column with '-N skip'
Reported by: | francoisb | Owned by: | mcayland |
---|---|---|---|
Priority: | medium | Milestone: | |
Component: | utils/loader-dumper | Version: | 2.0.x |
Keywords: | Cc: |
Description
The loader offers a command line option
-N skip
to skip features with null geometries. It would make sense the generated PostgreSQL table has a NOT NULL constraint set on the geometry column, since this is exactly what the user wants when specifying this option.
Note:
See TracTickets
for help on using tickets.
I don't agree. Often times I load in data with plan to add data later. I don't necessarily plan to load data with not null geometries since I sometimes add the attribute data first and then update from another table with a geometry. I see this as missplaced in -N skip (confusing doing too much when not asked for) and just as easy for a user to do themselves.