<?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: KeyWord Syntax in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/KeyWord-Syntax/m-p/832195#M292818</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;During script execution these differences will have no impact, I would say whichever you go with, be consistent and use use them across the whole script. Mixing your upper and lower cases around just looks a bit messy! &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Jun 2015 13:18:15 GMT</pubDate>
    <dc:creator />
    <dc:date>2015-06-16T13:18:15Z</dc:date>
    <item>
      <title>KeyWord Syntax</title>
      <link>https://community.qlik.com/t5/QlikView/KeyWord-Syntax/m-p/832192#M292815</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #575757; text-decoration: underline;"&gt;Performance associated with Syntax&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When typing in KeyWord syntax in QlikView the KeyWord will be provided in various text formats to choose from (i.e. some all upper, some mixed case, some all lower case).&amp;nbsp; Even so, majority of the typed KeyWords used are accepted, for Example LOAD (is all upper per QlikView), but &amp;lt; load &amp;gt; or &amp;lt; Load &amp;gt; are accepted.&amp;nbsp; I heard sticking to the exact KeyWords is best practice in your code (backend and frontend)&amp;nbsp; and will provide the best performance, is this true?&amp;nbsp; As the underlying code must do additional translations if you deviate from the provided exact syntax. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have used: (exambles of deviations)&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;'AS' when QlikView suggests 'as'&lt;/LI&gt;&lt;LI&gt;'Load' when Qlikview suggest 'LOAD'&lt;/LI&gt;&lt;LI&gt;'If' when Qlikview suggests 'IF'&lt;/LI&gt;&lt;LI&gt;'Drop Table' when QlikView suggests 'DROP Table'&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jun 2015 13:03:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/KeyWord-Syntax/m-p/832192#M292815</guid>
      <dc:creator>bjsellers57</dc:creator>
      <dc:date>2015-06-16T13:03:03Z</dc:date>
    </item>
    <item>
      <title>Re: KeyWord Syntax</title>
      <link>https://community.qlik.com/t5/QlikView/KeyWord-Syntax/m-p/832193#M292816</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't know if the upper or lower case makes a performance difference.&lt;/P&gt;&lt;P&gt;what I do know is that Sum(Sales( and sum(Sales) for example are different expressions for QlikView, so the server does not use it's cache to evaluate them but creates separate cache for each.&lt;/P&gt;&lt;P&gt;That has a performance impact, especially for complicated expressions or high data volume.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jun 2015 13:11:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/KeyWord-Syntax/m-p/832193#M292816</guid>
      <dc:creator>giakoum</dc:creator>
      <dc:date>2015-06-16T13:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: KeyWord Syntax</title>
      <link>https://community.qlik.com/t5/QlikView/KeyWord-Syntax/m-p/832194#M292817</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bernard,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;EM&gt;Case sensitivity will not reflect performance in Qlikview.&lt;/EM&gt;&lt;/SPAN&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But yes this is best practice which helps to make understand/highlight operations performed in coding &amp;amp; a reader can easily identify it. But there is no relation between Case sensitive keywords and performance of script.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But as a good programmer, one should keep habit of writing a neat &amp;amp; clean code with proper+simple syntax.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Complicated/Nested syntax affects on performance of application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer below link for more &amp;amp; better understandings.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/servlet/JiveServlet/previewBody/7343-102-1-9596/Best Practices in Data Modeling.pdf" title="https://community.qlik.com/servlet/JiveServlet/previewBody/7343-102-1-9596/Best%20Practices%20in%20Data%20Modeling.pdf"&gt;https://community.qlik.com/servlet/JiveServlet/previewBody/7343-102-1-9596/Best%20Practices%20in%20Data%20Modeling.pdf&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prashant P Baste&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jun 2015 13:17:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/KeyWord-Syntax/m-p/832194#M292817</guid>
      <dc:creator>prashantbaste</dc:creator>
      <dc:date>2015-06-16T13:17:59Z</dc:date>
    </item>
    <item>
      <title>Re: KeyWord Syntax</title>
      <link>https://community.qlik.com/t5/QlikView/KeyWord-Syntax/m-p/832195#M292818</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;During script execution these differences will have no impact, I would say whichever you go with, be consistent and use use them across the whole script. Mixing your upper and lower cases around just looks a bit messy! &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jun 2015 13:18:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/KeyWord-Syntax/m-p/832195#M292818</guid>
      <dc:creator />
      <dc:date>2015-06-16T13:18:15Z</dc:date>
    </item>
  </channel>
</rss>

