Re: [sqlite] Question about C# with SQLite

2016-07-07 Thread Shouwei Li
oops! This is exactly the solution. Thank you soo much! On Tue, Jul 5, 2016 at 3:50 PM, Chris Locke wrote: > Possible solution from StackOverflow: > Try setting the Build Action property of the source DLLs to None > > On Tue, Jul 5, 2016 at 1:18 PM, Shouwei Li

Re: [sqlite] Formal specification for sqlite3 file format

2016-07-07 Thread Bayer
The British National Archives has registered SQLite3 among its identified file formats (see PRONOM at http://www.nationalarchives.gov.uk/pronom/Default.aspx) and given it the following PUID: fmt/729. The U.S. Library of Congress has included SQLite3 in its Recommended Formats Statement for

Re: [sqlite] Downloading SQLite issue

2016-07-07 Thread Richard Hipp
On 7/7/16, Alex Fender wrote: > When I download SQLite for Mac, when I extract the file out of the zip and > open, the files are damaged. How can I download a file that is not damaged? I click on the link using Firefox and it downloads and unzips to my Mac just fine.

[sqlite] Downloading SQLite issue

2016-07-07 Thread Alex Fender
When I download SQLite for Mac, when I extract the file out of the zip and open, the files are damaged. How can I download a file that is not damaged? -- Alex Fender Funnel Scientist *Funnel Science Internet Marketing LLC * *Office* 972-867-3100 <%28972%29%20867-3100> *| Cell* 214-625-9023

Re: [sqlite] Formal specification for sqlite3 file format

2016-07-07 Thread Richard Hipp
On 7/7/16, Henry Chan wrote: > Dear all, > > I'm wondering if there is any "formal" specification for the sqlite3 > application format, as in standardized as an ISO/IEC standard, ECMA > standard or RFC? How does one go about getting a long-established file format

Re: [sqlite] sqldiff wrong quoting

2016-07-07 Thread Richard Hipp
On 7/6/16, Francesco Frassinelli wrote: > Hi, > it looks like sqldiff can't handle special characters like `%`: Thanks. Bug fixed here: https://www.sqlite.org/src/info/8bb8d886ffa948cd > > $ sqlite3 %.db > SQLite version 3.13.0 2016-05-18 10:57:30 > Enter ".help" for usage

Re: [sqlite] Help Installing SQLite on a Windows 8.1 PC

2016-07-07 Thread Donald Griggs
Hi Krista, Regarding: I have downloaded the two 64-bit Windows files on my Windows 8.1 PC, Are you referring to sqlite.exe and maybe sqlite.dll ? Regarding: but I cannot get SQLite to install on my PC. I'm not sure I understand you. Maybe you could rewrite this in form of something

[sqlite] Help Installing SQLite on a Windows 8.1 PC

2016-07-07 Thread Krista M Whipple
Dear SQLite Users, I am in a Predictive Analytics course which requires the use of SQLite. I am not a developer or an analyst and have zero hands on experience with working with software for databases. I have downloaded the two 64-bit Windows files on my Windows 8.1 PC, but I cannot get

[sqlite] Formal specification for sqlite3 file format

2016-07-07 Thread Henry Chan
Dear all, I'm wondering if there is any "formal" specification for the sqlite3 application format, as in standardized as an ISO/IEC standard, ECMA standard or RFC? This is similar to .DOCX being registered as both ISO/IEC 29500 and ECMA-376; JSON being RFC 7159 and ECMA-404, XML being a W3C

[sqlite] sqldiff wrong quoting

2016-07-07 Thread Francesco Frassinelli
Hi, it looks like sqldiff can't handle special characters like `%`: $ sqlite3 %.db SQLite version 3.13.0 2016-05-18 10:57:30 Enter ".help" for usage hints. sqlite> CREATE TABLE test (`%` REAL); sqlite> $ sqldiff %.db %.db sqldiff: SQL statement error: unrecognized token: """ "SELECT B.rowid, 1,

Re: [sqlite] Question about C# with SQLite

2016-07-07 Thread Chris Locke
Possible solution from StackOverflow: Try setting the Build Action property of the source DLLs to None On Tue, Jul 5, 2016 at 1:18 PM, Shouwei Li wrote: > Hi, guys, > > Thank you very much for your reply. > > Just make a conclusion, I followed the solution provided in this

Re: [sqlite] SQLite Logo

2016-07-07 Thread Chris Locke
Blimey - arguments over a feather, However, I want to argue about your "They look nothing alike" and I would say to a non-feather expert, they are very similar. Same orientation (upwards, pointing to the right), white middle, a nick on the right. They do look alike ... very alike. Chris On

Re: [sqlite] builtin functions and strings with embedded nul characters

2016-07-07 Thread James K. Lowden
On Mon, 4 Jul 2016 13:07:18 +0200 R Smith wrote: > I think you are missing an important bit in all of this - the strings > in C is the problem, they think a Null character indicates > termination. It has nothing to do with how SQL stores data - SQLite > will store it with all

Re: [sqlite] Extending Porter Tokenizer

2016-07-07 Thread Matthias-Christian Ott
On 2016-07-05 18:11, Abhinav Upadhyay wrote: > I'm wondering if it is possible to extend the functionality of the > porter tokenizer. I would like to use the functionality of the Porter > tokenizer but before stemming the token, I want to decide whether the > token should be stemmed or not. > >

Re: [sqlite] Query Flattener vs. result-set column names

2016-07-07 Thread Clemens Ladisch
Simon Slavin wrote: > On 7 Jul 2016, at 3:37pm, Josef Kučera wrote: >> Imagine a query like "SELECT A.F1, B1.F FROM A JOIN (SELECT F2 AS F FROM B >> WHERE F3=0) B1". > > your natural JOIN is a little dangerous since it can collapse if you > change column names or

Re: [sqlite] Query Flattener vs. result-set column names

2016-07-07 Thread Hick Gunter
The returned column names depend on the exact path taken in the query optimizer. This may change if the shape of your data changes (analyze is run). The SQL standard only requires that column references be either unique or qualified by table. -Ursprüngliche Nachricht- Von:

Re: [sqlite] Query Flattener vs. result-set column names

2016-07-07 Thread Josef Kučera
- Original Message - From: "Simon Slavin" To: "SQLite mailing list" Sent: Thursday, July 07, 2016 5:11 PM Subject: Re: [sqlite] Query Flattener vs. result-set column names On 7 Jul 2016, at 3:37pm, Josef Kučera

Re: [sqlite] Query Flattener vs. result-set column names

2016-07-07 Thread Simon Slavin
On 7 Jul 2016, at 3:37pm, Josef Kučera wrote: > Imagine a query like "SELECT A.F1, B1.F FROM A JOIN (SELECT F2 AS F FROM B > WHERE F3=0) B1". If the query flattener is active the result-set has columns > "A.F1" and "B1.F". If it is disabled the result-set columns are

[sqlite] Query Flattener vs. result-set column names

2016-07-07 Thread Josef Kučera
Hello, today I have discovered a strange side-effect of a query flattener. Imagine a query like "SELECT A.F1, B1.F FROM A JOIN (SELECT F2 AS F FROM B WHERE F3=0) B1". If the query flattener is active the result-set has columns "A.F1" and "B1.F". If it is disabled the result-set columns are "F1"