On Fri, Aug 30, 2019 at 3:35 PM Keith Medcalf wrote:
> Seems fine, other than that event.first_seen and event.last_seen can be NULL,
> in which case that field will never be updated. So while you may claim that
> you never store NULL in those fields, doing so will cause non-workage due to
>
On Friday, 30 August, 2019 14:45, Random Coder wrote:
>CREATE TABLE IF NOT EXISTS
>event(
>event_id TEXT PRIMARY KEY,
>first_seen INTEGER,
>last_seen INTEGER
>) WITHOUT ROWID;
So first_seen and last_seen are permitted to be NULL?
>
First off, if this sort of "code review" style question is
inappropriate for this list, please feel free to reply to me directly
and tell me to stop, and I'll know to not do this again.
That said, I have a question on the use of SQLite. At the risk of
falling into the XY problem, I'll give some
When you run ".open test.db" if the database doesn't already exist, then the
file is created. However *no data is written yet* as there are a few permanent
things you could change at the very start (like page size, encoding, etc), so
it holds off on writing the first page with the header until
Running sqlite3 will open up an in-memory database to start with.
".open test" will either open the file "test" if it exists, or create the file
if it doesn't. You will then be working on that file called "test" which is
your database.
The help line for .save is:
.save FILE Write
On 8/30/19 9:11 AM, Alexander Gabriel wrote:
> Hi
>
> I do this:
>
>- restart windows10 or macOS and log in (to guarantee no other process
>is using sqlite3)
>- cd to the folder where sqlite3 v3.29.0 is contained
>- type `sqlite3` (windows 10) or `./sqlite3` (macOS) to start
Hi
I do this:
- restart windows10 or macOS and log in (to guarantee no other process
is using sqlite3)
- cd to the folder where sqlite3 v3.29.0 is contained
- type `sqlite3` (windows 10) or `./sqlite3` (macOS) to start sqlite3
- type `.open test`, followed by `.save test`
Result:
Hi
*error: unable to read database header*
Sorry for spamming this list but as it is an email list I cannot add to my
original issue as for instance in github.
As mentioned in my previous email I have donwloaded binaries for windows
10, run `.open test` followed by `.dbinfo` and got this error:
Hi
I downloaded the files for v3.29.0 into a folder.
Then double clicked sqlite3.exe to open a command shell.
Then typed `.open test.db`
Then typed `.dbinfo`
And got: `unable to read database header`
What am I doing wrong?
Have I created a broken database?
Alex
On 8/30/19 3:42 PM, David Raymond wrote:
> Sorry if my mind is working slowly today, but why are those showing up as a
> difference when they're exactly the same line?
>
>
> The only difference between both runs:
>> $ diff run1 run2
>> 1260d1259
>> < INSERT INTO space_used
>>
Sorry if my mind is working slowly today, but why are those showing up as a
difference when they're exactly the same line?
The only difference between both runs:
> $ diff run1 run2
> 1260d1259
> < INSERT INTO space_used
>
> From: Free Ekanayaka, on Thursday, August 29, 2019 10:21 AM, wrote...
>
> Hello Jose,
>
> Jose Isaias Cabrera, on
> > which lets me know that it linux/unix based. But, is Windows an
> > option also? Thanks.
>
> At the moment Windows is not an option, mainly because under the hood
> dqlite
Hi,
please add to the documentation that column limited phrase search is not
supported by FTS3 and FTS4.
Example:
CREATE VIRTUAL TABLE FTSTable USING FTS3 (content,body);
SELECT * FROM FTSTable WHERE FTSTable MATCH 'content:"one two"';
Does not result in an error but also returns no results.
Hi,
yes, but unfortunately I have still a project using FTS3 tables to which I have
to add new features..
Regards,
Hardy
> Am 2019-08-30 um 13:00 schrieb Dan Kennedy :
>
>
> On 30/8/62 17:39, mailing lists wrote:
>> Hi,
>>
>> but there is no token '^beta'! Even if in FTS3 '^' is not
On 30/8/62 17:39, mailing lists wrote:
Hi,
but there is no token '^beta'! Even if in FTS3 '^' is not regarded as a special
character. Is the '^' removed by the tokenizer?
Right. It's removed by the tokenizer.
FTS3/4 is focused on backwards compatibility. New work should really use
FTS5 -
Hi,
I think that I have to be more specific here. Only under certain configurations
this MATCH-clause does not work (example):
CREATE VIRTUAL TABLE myDATA USING FTS3 (one,two,three,four);
SELECT * FROM myData m1, myData m2 WHERE m1.myData MATCH 'one: 42*' AND
m2.myData MATCH 'two: alpha';
Hi,
but there is no token '^beta'! Even if in FTS3 '^' is not regarded as a special
character. Is the '^' removed by the tokenizer? Because it is regarded as a
diacritical character?
PS: I have to admit that I have overlooked the comment that '^' works only for
FTS4 tables.
Regards,
Hardy
>
The fts3/4 documentation says:
"If the FTS table is an FTS4 table (not FTS3), a token may also be
prefixed with a "^" character. In this case, in order to match the token
must appear as the very first token in any column of the matching row."
So change "FTS3" to "FTS4" and it will likely
Hi,
I could not find an example showing a result in the documentation, therefore I
created one by myself:
CREATE VIRTUAL TABLE myData USING FTS3(content);
INSERT INTO myData 'alpha beta';
1)
SELECT * FROM myData WHERE myData MATCH 'beta';
Result:
content
alpha beta
This is what I expected.
Because of my (obviously wrong) automatic query generator I came across this
issue:
CREATE VIRTUAL TABLE myData USING FTS3 (content, body);
SELECT * FROM myData WHERE (content MATCH 'one') AND (body MATCH 'two');
What is the reason that the above query is not allowed and that
SELECT * FROM
20 matches
Mail list logo
