On 11/8/17, korablev wrote:
> What is the timeline of this feature? Will it be implemented in the nearest
> future?
Low priority. I do not like automatic index feature, because I think
that app developers should do an appropriate CREATE INDEX instead. Of
course, it is not possible to a CREATE I
What is the timeline of this feature? Will it be implemented in the nearest
future? And what optimizations doesn't also work on without rowid tables? Is
the query planner good at optimizing stuff on without rowid tables at all?
--
Sent from: http://sqlite.1065341.n5.nabble.com/
_
On 11/8/17, Peter Da Silva wrote:
> On 11/8/17, 8:20 AM, "sqlite-users on behalf of Richard Hipp"
>
> wrote:
>> The technical reason for this is that, from the point of view of the query
>> planner, a WITHOUT ROWID table is really a covering index
>
> So basically the whole table is stored inline
On 11/8/17, 8:20 AM, "sqlite-users on behalf of Richard Hipp"
wrote:
> The technical reason for this is that, from the point of view of the query
> planner, a WITHOUT ROWID table is really a covering index
So basically the whole table is stored inline with the primary key index?
_
On 11/8/17, korablev wrote:
> sqlite> create table t1(a primary key, b) without rowid;
> sqlite> create table t2(a primary key, b) without rowid;
> sqlite> explain query plan select * from t1, t2 where t1.b = t2.b;
> 0|0|0|SCAN TABLE t1
> 0|1|1|SCAN TABLE t2
> sqlite> create table t3(a primary key
sqlite> create table t1(a primary key, b) without rowid;
sqlite> create table t2(a primary key, b) without rowid;
sqlite> explain query plan select * from t1, t2 where t1.b = t2.b;
0|0|0|SCAN TABLE t1
0|1|1|SCAN TABLE t2
sqlite> create table t3(a primary key, b);
sqlite> create table t4(a primary k
6 matches
Mail list logo