[fdo-trac] #454: Insert commands seriously messed up when null values are omitted

[FDO]

#454: Insert commands seriously messed up when null values are omitted
-----------------------------+----------------------------------------------
 Reporter:  jng              |         Owner:  traianstanev
     Type:  defect           |        Status:  assigned    
 Priority:  critical         |     Milestone:  3.4.0       
Component:  SQLite Provider  |       Version:  3.4.0       
 Severity:  1                |    Resolution:              
 Keywords:                   |   External_id:              
-----------------------------+----------------------------------------------
Changes (by traianstanev):

  * priority:  blocker => critical
  * status:  new => assigned

Comment:

 Yes, this is a defect because of the way reusing of the same Insert
 command is internally optimized for bulk insert. However, it is not a
 blocker, since there are multiple workarounds -- you can either include
 all the properties in the property value collection from the start and set
 the right ones to null, or you can create a new insert command when the
 set of properties changes. I'll look into what can be done without
 compromising the bulk insert optimizations.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/454#comment:1>
FDO <http://fdo.osgeo.org/>
Feature Data Objects