On Jan 28, 2019, at 2:44 PM, Chris Locke <sql...@chrisjlocke.co.uk> wrote: > >> The table name should not be meaningful to your application; nothing in >> your application should conjure up a table name. > > I can't get my head around this advice. Is this just for this occasion, or > for every application? What if I'm writing a customer address book? Am I > allowed a table called 'customers' ? Thats meaningful to my application. > Not sure what your trying to advise here.
He’s saying that if your customer is called Bill The Cat, you should not call the table holding that customer’s records “Bill the Cat”. How else do you end up with 20000 tables in a single database, each created on the fly based on some unspecified event, as the OP talks about? _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
