Thank you very much for the responses. That was helpful.


With best regards,
Christoph Brzozowski

Siemens AG
Industry Sector
Industry Automation Division
Industrial Automation Systems
Process Automation
I IA AS PA CIS R&D 5
Karl-Legien-Str. 190
53117 Bonn, Germany
Tel: +49 228 64805-215
mailto:christoph.brzozow...@siemens.com

Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme; 
Managing Board: Joe Kaeser, Chairman, President and Chief Executive Officer; 
Roland Busch, Brigitte Ederer, Klaus Helmrich, Barbara Kux, Hermann Requardt, 
Siegfried Russwurm, Peter Y. Solmssen, Michael Suess; Registered offices: 
Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 
12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322
-----Original Message-----
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] 
On Behalf Of Joe Mistachkin
Sent: Donnerstag, 5. September 2013 08:08
To: 'General Discussion of SQLite Database'
Subject: Re: [sqlite] Different read/write behaviour when using 
System.Data.SQLite .NET Wrapper and using database encryption through a 
password leads to data inconsistency


Brzozowski, Christoph wrote:
>
> Our application uses the System.Data.SQLite .NET Wrapper ( version
1.0.66.0 )
>

That version was released in April 2010 and is no longer officially supported.

> 
> in a multi user scenario, where multiple users on different machines
access the
> same database, which lies on a network share, or in a single user
scenario, where
> the database lies locally but is accessed simultaneously by multiple
processes
> on the same machine. 
> 

Sharing a SQLite database file using a network share on Windows can be 
problematic, please refer to the following link for further information:

        https://www.sqlite.org/faq.html#q5

> 
> When we switched the database to an encrypted one, by adding a 
> password to
the
> connection string passed to the ADO.NET Sqlite provider, the
synchronization
> mechanisms ceased to work. 
> 

The CryptoAPI-based encryption included with System.Data.SQLite is a legacy 
feature, has known issues, and is officially unsupported.  It is being retained 
only for the purpose of backward compatibility with legacy applications that 
make use of it.

That all being said, you might wish to try using the latest released version of 
System.Data.SQLite.

Alternatively, you might want to look into the commercial SEE extension, which 
does work with System.Data.SQLite and is fully supported for use with it.

--
Joe Mistachkin

_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to