> On Aug 28, 2018, at 1:22 PM, David Raymond wrote:
>
> Embarrassing confession time: I didn't think you could use "using" to do this
> while selecting "a.*"
>
> https://www.sqlite.org/lang_select.html
> "For each pair of columns identified by a USING clause, the column from the
> right-hand
SQLITE_USE_URI
If this is not defined then URI's are not parsed.
https://www.sqlite.org/uri.html
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
Hi there,
I've been using in-memory SQLite database for the automated tests in an
application I'm writing. I did most of the initial development on macOS and
things worked as I expected, but when I ran the tests on my Linux box it
left behind files like "file:test-3210?mode=memory=shared".
On my
On 2018/08/28 7:18 PM, Jay Kreibich wrote:
On Aug 28, 2018, at 11:30 AM, Joe wrote:
A (perhaps silly ) beginners question:
My sqlite database contains several tables, two of them, table A and table B,
have text colums called 'nam'. The tables have about 2 millions lines.
What's the most
Embarrassing confession time: I didn't think you could use "using" to do this
while selecting "a.*"
https://www.sqlite.org/lang_select.html
"For each pair of columns identified by a USING clause, the column from the
right-hand dataset is omitted from the joined dataset. This is the only
> On Aug 28, 2018, at 11:30 AM, Joe wrote:
>
> A (perhaps silly ) beginners question:
> My sqlite database contains several tables, two of them, table A and table B,
> have text colums called 'nam'. The tables have about 2 millions lines.
> What's the most efficient way to select all lines
On 28 Aug 2018, at 5:32pm, Richard Hipp wrote:
> I suppose:
>
> SELECT * FROM A WHERE nam NOT IN (SELECT nam FROM B);
Depending on how many names the tables have in column, a possible alternative
might be to use the EXCEPT compound operator here. Something like
SELECT nam FROM A
On 8/28/18, Joe wrote:
> A (perhaps silly ) beginners question:
> My sqlite database contains several tables, two of them, table A and
> table B, have text colums called 'nam'. The tables have about 2
> millions lines.
> What's the most efficient way to select all lines from table A with nam
>
A (perhaps silly ) beginners question:
My sqlite database contains several tables, two of them, table A and
table B, have text colums called 'nam'. The tables have about 2
millions lines.
What's the most efficient way to select all lines from table A with nam
values, which are not present in
On 28 Aug 2018, at 15:36, Keith Medcalf wrote:
> On Tuesday, 28 August, 2018 07:50, Tim Streater wrote:
>>How does it know not to do that if I want to send some binary data to a Text
>>column?
>
> Simply because you do not request that those things be done.
>
> So, the "things" that may occur
On Tuesday, 28 August, 2018 07:50, Tim Streater wrote:
>What is actually the difference between a column declared as TEXT and
>one declared as BLOB in an SQLite database?
Not a thing. You are free to store data of any type in any column in any row.
The "TEXT" declaration only means that
Ah great to know. Thanks!
Ben
On Tue, Aug 28, 2018 at 7:29 AM Richard Hipp wrote:
> On 8/28/18, Ben Asher wrote:
> > I seem to remember that BLOBs cannot be indexed. I can’t find
> documentation
> > on that though. Does anyone else recall the same thing and have a link,
> or
> > maybe someone
On 8/28/18, Ben Asher wrote:
> I seem to remember that BLOBs cannot be indexed. I can’t find documentation
> on that though. Does anyone else recall the same thing and have a link, or
> maybe someone can correct me?
You might be remembering the limitations of Oracle. Other database
engines
On 28 Aug 2018, at 2:50pm, Tim Streater wrote:
> What is actually the difference between a column declared as TEXT and one
> declared as BLOB in an SQLite database? What does SQLite do to textual data
> that I ask it to put into a TEXT column?
BLOB data is always handled as a block of a
On 2018-08-28 09:50:01, "Tim Streater" wrote:
What is actually the difference between a column declared as TEXT and
one declared as BLOB in an SQLite database? What does SQLite do to
textual data that I ask it to put into a TEXT column? How does it know
not to do that if I want to send some
I seem to remember that BLOBs cannot be indexed. I can’t find documentation
on that though. Does anyone else recall the same thing and have a link, or
maybe someone can correct me?
Ben
On Tue, Aug 28, 2018 at 6:50 AM Tim Streater wrote:
> What is actually the difference between a column
What is actually the difference between a column declared as TEXT and one
declared as BLOB in an SQLite database? What does SQLite do to textual data
that I ask it to put into a TEXT column? How does it know not to do that if I
want to send some binary data to a Text column?
The reason I'm
The correct syntax is:
CREATE INDEX dbondisk.diskIndex on TestTable (Parent)
See: https://sqlite.org/lang_createindex.html
On 2018/08/27 5:37 PM, Jiawei Duan wrote:
SQLite version: 3.24.0
System info: macOS 10.13.6
The following SQL commands results an error of "Error: near ".": syntax
SQLite version: 3.24.0
System info: macOS 10.13.6
The following SQL commands results an error of "Error: near ".": syntax error”.
However the command can proceed within the main database.
ATTACH DATABASE ‘/Users/***/test.db' AS dbondisk;
CREATE INDEX diskIndex on dbondisk.TestTable (Parent)
HAVING is only applicable to GROUP BY's. That is, the WHERE clauses constrain
what goes into the sorter for the "group by" operation and the HAVING clauses
constrain what comes out of the sorter from the "group by" operation and is
returned as a query result.
I think that the issue is that
In the sqlite shell, enter the .explain command and then
EXPLAIN QUERY PLAN
for an explanation of the plan, and
EXPLAIN
for the generated bytecode. This usually helps to understand what sqlite is
thinking (although maybe not why).
Note that WHERE constraints are applied to the input set
There are a myriad of reasons for the behaviour you are seeing and they affect
only performance and not correctness. In other words, you think that your UDF
is more "expensive" to compute than the PPID == 2 test, and therefore the least
expensive test should be performed first so that the
22 matches
Mail list logo
