News for hackers. Stuff that matters.
Re:SQLite 3.7.16 Released by xradionut on Tuesday March 19, 2013 @10:47AM (#5401183)
"In the new design a row's primary key directly contributes to its physical key, meaning lookups and iterations on the primary key involve only one scan (rather than an index scan followed by random lookups in SQLite 3.x/most DBMS)."

Isn't this basically the same concept as a clustered index in MS SQL Server?

Re:SQLite 3.7.16 Released by _wmd on Tuesday March 19, 2013 @10:50AM (#5401200)
Yep, although I'm not sure if clustering is also a hand-triggered process in SQL Server (like it is in e.g. PostgreSQL). In any case SQLite 4.x will do it automatically.
Re:SQLite 3.7.16 Released by Shorel on Tuesday March 19, 2013 @11:04AM (#5401289)
In SQL Server that's defined at table creation time.

In Oracle it's the same: defined at creation time, but you call it an Indexed Ordered Table (IOT).

In MySQL all InnoDB tables are clustered (in that sense) because that's the only storage strategy of InnoDB.