On 7 sep. 2013, at 04:45, "David de Regt" <[email protected]> wrote:
> Mayhaps the CROSS JOIN trick is your friend in this case, if you can be > pretty sure of the correct direction of the join order. :) In the examples I gave it was actually about a simple delete query from one table without any joins, so that still does not explain the huge performance decrease. > From: [email protected] > [mailto:[email protected]] On Behalf Of James K. Lowden > Sent: Friday, September 6, 2013 7:40 PM > To: [email protected] > Subject: Re: [sqlite] Query preperation time does not scale linearly with > growth of no. of tables > > Factorial, actually. After three tables, each addtional table increases > potential join sequences by roughly an order of magnitude. This factorial increasement would be the case if there were any joins, but there are none. Does any one have any other explanation to why the performance gets so bad when having many tables? Our table and column names are not too long either as E.Pasma suggests. Best regards, Harmen _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
