Though you probably COULD merge them all together there are situations where you don't want to. Just like his original question.
Imagine you have a bunch of tables of consumer products split by type. Yes, you could stick it all in one humogous database...but... The split allows you to reduce contention so that doing an update doesn't stop everybody and even reads will be faster since they are split. The bind allows you to use just one routine with a pre-prepared statement for speed instead of building your own sql string and having to prepare it each time. Seems like quite an upside to it to me unless I'm missing something (which is quite possible :-) Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems ________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Simon Slavin [slav...@bigfraud.org] Sent: Tuesday, November 01, 2011 9:10 AM To: General Discussion of SQLite Database Subject: EXT :Re: [sqlite] Indirect Referencing On 1 Nov 2011, at 2:01pm, Black, Michael (IS) wrote: > Hmmm...how hard would it be allow one to bind the table name with prepare? If you are in a position to bind the table name, does that not mean you could just merge all the tables together ? Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
