<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: strange alias in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/strange-alias/m-p/846770#M334739</link>
    <description>&lt;P&gt;In the way it appears here, it's optional.&lt;/P&gt;
&lt;P&gt;So it's pretty much up to the developer to decide the programming style.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Nov 2022 10:34:19 GMT</pubDate>
    <dc:creator>LinusH</dc:creator>
    <dc:date>2022-11-29T10:34:19Z</dc:date>
    <item>
      <title>strange alias</title>
      <link>https://communities.sas.com/t5/SAS-Programming/strange-alias/m-p/846760#M334732</link>
      <description>&lt;PRE&gt;Proc SQL;
    create  table acct_list_cen_limit_2A as 
    select org_code, account_no, LOGO, card_type, relationship_no,
    date_Credit_limit_chg as Date_Credit_limit_chg,
    ratio,
    p_credit_limit*Ratio as p_credit_limit,
    IND_CENTRAL_LIMIT,
    FIRST_DEFAILT,
    SAMP_OS,
    SAMP_CRLIM*RATIO as SAMP_CRLIM,
    PBI_BALANCE as PBI_BALANCE,
    DEFAULT_AMT AS DEFAULT_AMT,
    SAMP_CRLIM_ALL*RATIO AS SAMP_CRLIM_ALL,
    MONTH_DEF AS MONTH_DEF,
    PORTFOLIO AS PORTFOLIO,
    REL_CNT AS REL_CNT
FROM ACCT_LIST_CEN_LIMIT_2;
QUIT;

    
&lt;/PRE&gt;
&lt;P&gt;Why are some variables being renamed to the same name? what does this mean?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 09:12:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/strange-alias/m-p/846760#M334732</guid>
      <dc:creator>HeatherNewton</dc:creator>
      <dc:date>2022-11-29T09:12:26Z</dc:date>
    </item>
    <item>
      <title>Re: strange alias</title>
      <link>https://communities.sas.com/t5/SAS-Programming/strange-alias/m-p/846770#M334739</link>
      <description>&lt;P&gt;In the way it appears here, it's optional.&lt;/P&gt;
&lt;P&gt;So it's pretty much up to the developer to decide the programming style.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 10:34:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/strange-alias/m-p/846770#M334739</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2022-11-29T10:34:19Z</dc:date>
    </item>
    <item>
      <title>Re: strange alias</title>
      <link>https://communities.sas.com/t5/SAS-Programming/strange-alias/m-p/846861#M334796</link>
      <description>&lt;P&gt;Why the coder decided to use&amp;nbsp;"date_Credit_limit_chg as Date_Credit_limit_chg" instead of just "date_Credit_limit_chg" you would need to ask the coder directly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note that there are no aliases being used in that code.&amp;nbsp; In SQL jargon the ALIAS is the short name assign to an input dataset so you have it as a prefix when referencing a variable to make sure that SQL knows which source dataset the variable should come from.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If this example A and B are the aliases:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;proc sql;
create table want as
  select a.name,b.address
  from names a
  left join address b 
  on a.name=b.name
;
quit;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 17:19:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/strange-alias/m-p/846861#M334796</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2022-11-29T17:19:52Z</dc:date>
    </item>
  </channel>
</rss>

