[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:              
-----------------------------+----------------------------------------------
Comment (by traianstanev):

 Here are more details on the problem... If you change the contents of the
 property value collection of the insert command, after having executed the
 insert command once, you are asking for trouble, because the provider
 caches a pre-compiled parametrized SQL statement based on the state of the
 property value collection during the first time you Execute(). Note that
 you can change the actual values, just not the set of property values in
 the collection. The two workarounds described in the previous note will
 avoid that problem.

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