On 10 Jul 2010, at 5:39pm, Calimeron wrote: > -- One table is more than 30.000 lines, the other is more than 50.000 lines. > I've understood from the video tutorial that the program (I'm using > http://www.sqlite.org/sqlite-3_6_23_1.zip) will first compile the entire > list 30.000 x 50.000 = 1.5 BILLION lines, after which it filters it. I'm > sure that's too many lines? (My firefox plugin repeatedly crashed, so I > switched to this one.)
If you're talking about the command-line tool 'sqlite3', then it saves the table to disk as it works. It does not generate the entire table to memory, then store it to disk as a single operation. On 10 Jul 2010, at 6:10pm, Eric Smith wrote: > But the view, as far as I understand, doesn't provide a performance > benefit over the query that defines it. It only exists for simplified > understanding of your problem space and your code. In SQLite, a VIEW is a way of saving a SELECT command. It saves the command itself, not the results of running it. So yes, you're right: a VIEW would not involve storing the entire resulting table in memory. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
