[PATCH 2/2] Added SQLite history plugin

[Nicola Mfb]

On Wed, Apr 7, 2010 at 7:01 PM, Denis Kenzior <denkenz at gmail.com> wrote:
[...]
>> Database connection is handled by sqlite3_* API in a transparent manner
>> so you could have different open connections at the same time without
>> any problem, each SQL statement is transactional so the DB is every time
>> consistent, but if you prefer I can rethink of it (maybe a DB for every
>> modem could be a possibility but this would overload the plugin because
>> we have to open and close the DB in every callback given that we have to
>> filter the files access by modem).
>
> My concern here was that multiple open connections to the same database might
> require locking or other overhead that could be avoided with a single shared
> connection.  It might be there is no overhead and your original approach is
> fine.

What's about a dbfile for each modem? we'll have one connection per
database, and may avoid the "modem" column on all the tables, saving
storage space.

[...]

> We're working on improving the SMS capabilities, and might eventually expose
> the message id.  However, the message id really has no meaning, so this is not
> something we really want to expose.  I'd like to keep it private between the
> history plugin and the core.  Are you sure you really require it to be
> exposed, or can you do without it?

We prefer to have the id to easily sync with the history plugin, as
said in previous mail, if you prefer to not expose the id on
IncomingMessage, we may emit an HistoryIncomingMessage signal with the
id.

Regards

     Niko