On Jan 20, 2014, at 5:23 PM, Jonathan Vanasco <[email protected]> wrote:
> 2. it doesn't affect the label/aliasing on the table, just the column . ie, > > SELECT mytable.id AS _1 FROM mytable > > not > > SELECT _t1.id AS _1 FROM mytable _t1 that it can’t do. an Alias is a very different object than a Table. to do that transparently without much more elaborate SQL constructs being produced would require some kind of logic akin to the “join rewriting” feature used by the SQLite dialect; this kind of adaptation of SQL on the fly to something structurally different is extremely difficult to do. not at all worth it here. I don’t really think this is the path that’s going to get you 1-2% more CPU freedom. There’s other ways, like caching entire statements that can go a lot further. Or switching to Pypy would save you an enormous amount as it benches pretty much twice as fast as cPython now.
signature.asc
Description: Message signed with OpenPGP using GPGMail
