On Jan 20, 2014, at 4:32 PM, Jonathan Vanasco <[email protected]> wrote:
> i'm just wondering for performance over-the-wire from the bandwidth alone... > > > I see great, DBA & toubleshooting friendly stuff like: > > SELECT table_one.column_one AS table_one_column_one FROM table_one ; > > but that could be... > > SELECT t1.column_1 AS t1_column_1 FROM table_one t1; > > or even > > SELECT t1.column_1 AS t1_c1 FROM table_one t1; > > it's silly on my one column select, but looking at some other selects i have > in the wild -- my selects are roughly 6x what they could be. 6x… what, longer from a string name perspective? if you really cared, there’s a setting called label_length (http://docs.sqlalchemy.org/en/rel_0_9/core/engines.html?highlight=create_engine#sqlalchemy.create_engine.params.label_length) which will shorten the label names down to 6 characters at the lowest. > i'm just wondering if this was avoided from philosophy or design -- i can > imagine the aliasing and un-aliasing getting very intricate and convoluted in > more intense queries. the aliasing has no fixed reliance upon the actual syntax of the label string! which was not easy to do, but that’s how we have cool features like label_length.
signature.asc
Description: Message signed with OpenPGP using GPGMail
