#2851: v.in.ogr: imports empty values as empty strings instead of NULL values
--------------------------+----------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.3
Component: Default | Version: svn-trunk
Resolution: | Keywords: vector v.in.ogr null
CPU: Unspecified | Platform: Unspecified
--------------------------+----------------------------------
Comment (by marisn):
Although I am more purist and would say that NULL should be NULL, here's
opinion why "no data" should be text (from Django framework):
"Avoid using null on string-based fields such as CharField and TextField
because empty string values will always be stored as empty strings, not as
NULL. If a string-based field has null=True, that means it has two
possible values for “no data”: NULL, and the empty string. In most cases,
it’s redundant to have two possible values for “no data;” the Django
convention is to use the empty string, not NULL."
https://docs.djangoproject.com/en/1.9/ref/models/fields/#null
If it comes down to voting, my vote goes for keeping NULL as NULL (do not
alter data unless asked for).
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2851#comment:2>
GRASS GIS <https://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
