Re: [sqlite] Best way to set default PRAGMA's in System.Data.SQLite

2019-06-08 Thread Joe Mistachkin
Sam Carleton wrote: > > I am trying out this approach right now and running into one minor issue, > the following cmd only builds the debug version: > > msbuild SQLite.NET.2015.MSBuild.sln /p:UseSqliteStandard=true > /p:UseInteropDll=false > Have you tried using the "build.bat" tool in the

Re: [sqlite] Best way to set default PRAGMA's in System.Data.SQLite

2019-06-08 Thread Sam Carleton
On Sat, Jun 1, 2019 at 7:35 PM Joe Mistachkin wrote: > > compile the System.Data.SQLite assembly in such a way that it uses a > "standard" SQLite > DLL, via setting the following MSBuild properties: > > /p:UseSqliteStandard=true /p:UseInteropDll=false > Joe, I am trying out this

[sqlite] compiling System.Data.SQLite and using it across VS versions...

2019-06-08 Thread Sam Carleton
So my system using SQLite consists of multiple executables. One is a VS2015 .Net 4.6.2 app, there are two more that are VS2008 C++ applications. At the moment I am using the officially compiled version of System.Data.SQLite for the VS2015 program, and compiling sqlite.dll for the VS2008 C++

Re: [sqlite] Failing SQLite .import returns exit status 0

2019-06-08 Thread Gerry Snyder
A constraint doing its job is not an error. On Fri, Jun 7, 2019, 7:49 PM Faheem Mitha wrote: > > Hi, > > Consider the following shell script: > > rm -f empty.db empty.csv > echo "" > empty.csv > echo "a, b" >> empty.csv > sqlite3 empty.db \ > 'DROP TABLE IF EXISTS empty;' \ > '.mode csv' \ >

Re: [sqlite] Failing SQLite .import returns exit status 0

2019-06-08 Thread Simon Slavin
On 8 Jun 2019, at 4:15pm, Adrian Ho wrote: > Except...it's not bailing on the failed import. Does the SQLite shell > consider failed dot-commands as errors? That's not what I expected. One for the developers. ___ sqlite-users mailing list

Re: [sqlite] Failing SQLite .import returns exit status 0

2019-06-08 Thread Adrian Ho
On 8/6/19 9:26 PM, Simon Slavin wrote: > Use > > .bail ON > > If the shell bails out because of an error, it should be setting the exit > code to indicate an error. Except...it's not bailing on the failed import. Does the SQLite shell consider failed dot-commands as errors? $ cat empty.sh

Re: [sqlite] Failing SQLite .import returns exit status 0

2019-06-08 Thread Luuk
On 8-6-2019 15:26, Simon Slavin wrote: Use .bail ON If the shell bails out because of an error, it should be setting the exit code to indicate an error. unfortunatly still 0 is returned  (sqlite3 version 3.28.0) ~/temp> cat empty.sh #!/bin/bash rm -f empty.db empty.csv echo "" >

Re: [sqlite] Failing SQLite .import returns exit status 0

2019-06-08 Thread Simon Slavin
Use .bail ON If the shell bails out because of an error, it should be setting the exit code to indicate an error. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] Failing SQLite .import returns exit status 0

2019-06-08 Thread Adrian Ho
On 8/6/19 10:49 AM, Faheem Mitha wrote: > rm -f empty.db empty.csv > echo "" > empty.csv > echo "a, b" >> empty.csv > sqlite3 empty.db \ > 'DROP TABLE IF EXISTS empty;' \ > '.mode csv' \ > 'CREATE TABLE IF NOT EXISTS empty(A, B NOT NULL);' \ > '.import empty.csv empty' '.exit' > echo "error code