On Mon, 3 Feb 2014 23:49:14 +0100 Petite Abeille <[email protected]> wrote:
> > I have a query > > Not directly related to your question, but? why oh why do people > molest their queries by gratuitously and pointlessly aliasing > perfectly good table name to meaningless random one letter codes?!? > Masochism? Hey! I'll allow gratuitious and pointless, but molest? And definitely not random. Even perfectly good table names can be quite long. I'm sure you've seen some more than 30 characters. Just the physical act of typing them is one drawback. Yes, I have heard about that cut-and-paste feature everyone's talking about these days. Slows me down, say I. SQL is hardly a monument to succinct expression. Shorter queries are *easier* to understand, all thing being equal. The trick is to avoid meaningless and arbitrary aliases. In a small query, a single letter taken from the first letter of the tablename usually works. For larger queries I usually lean on 3-letter abbreviations. Three letters is space enough for mnemonic aliases; it's enough for, say, all the world's airports and currencies. As Humpty-Dumpty said, "There's glory for you." --jkl _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
