On 8/23/06, Andrew McCollum <[EMAIL PROTECTED]> wrote:
I find this feature useful, especially in queries which use aggregate
functions, such as the following:
SELECT sum(a) FROM tbl GROUP BY b
The question should be what the compelling reason is to remove a useful
feature.
... And *that* is
On 8/21/06, John Salerno <[EMAIL PROTECTED]> wrote:
Hi guys. Is it possible to load a sql file that is for a MySQL
database into a SQLite database? Does it just work normally, or would
some tweaking be needed? Or does this just not work?
Usually you will need some tweaking. One particularly
On 8/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
"Jonathan Ellis" <[EMAIL PROTECTED]> wrote:
> sqlite> attach 'foo.db' as foo;
> sqlite> create table foo.bar (i int);
> sqlite> create index foo.bar_i on foo.bar(i);
Should be:
create index f
On 8/19/06, Gerry Snyder <[EMAIL PROTECTED]> wrote:
Jonathan Ellis wrote:
> (was the "+" some kind of shorthand I'm unfamiliar with?)
>
Yes. It tells sqlite not to use those fields as an index.
Ah, I see. When I tried "+f.mtime" it gave a "no such
On 8/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
"Jonathan Ellis" <[EMAIL PROTECTED]> wrote:
> When ordering by columns from two tables, sqlite isn't using the index
> on the first column.
>
> explain query plan SELECT *
> FROM files f, file_info
When ordering by columns from two tables, sqlite isn't using the index
on the first column.
explain query plan SELECT *
FROM files f, file_info fi
WHERE f.id = fi.file_id
ORDER BY f.name, fi.mtime;
0|0|TABLE files AS f
1|1|TABLE file_info AS fi WITH INDEX info_by_file
If I drop the secondary
sqlite> attach 'foo.db' as foo;
sqlite> create table foo.bar (i int);
sqlite> create index foo.bar_i on foo.bar(i);
SQL error: near ".": syntax error
sqlite>
Is there another way to do this?
-
To unsubscribe, send email
ns
ON users.name = loans.user_name
) ON books.id = LBID;
--- Jonathan Ellis <[EMAIL PROTECTED]> wrote:
> Not sure what's wrong with this SQL; it works fine with postgresql:
>
> sqlite> SELECT * FROM books LEFT OUTER JOIN (users JOIN loans ON
users.name=
> loans.user_name) ON
Not sure what's wrong with this SQL; it works fine with postgresql:
sqlite> SELECT * FROM books LEFT OUTER JOIN (users JOIN loans ON users.name=
loans.user_name) ON books.id = loans.book_id;
SQL error: no such column: loans.book_id
The table definitions are as follows:
CREATE TABLE books (
9 matches
Mail list logo
