I'm not sure if it fits to
SQLiteCommandBuilder
, but MSDN states:
Quote:
The DbCommandBuilder
must execute the SelectCommand
in order to return the metadata necessary to construct the INSERT
, UPDATE
, and DELETE
SQL commands. As a result, an extra trip to the data source is necessary, and this can hinder performance. To achieve optimal performance, specify your commands explicitly rather than using the DbCommandBuilder
.
Maybe...
SQLiteCommandBuilder
must to sucessfully get data first (by using
SelectCommand
) to be able to create proper
InsertCommand
.
I'd recommend to follow the tip provided by
ZurdoDev[
^]:
Quote:
Yes, use a regular SqlCommand object to create the table first.
For further details, please see:
Getting started with SQLite in C# – Tigran's Blog[
^]