<?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>Question Re: Update &amp; Join in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/update-join/qaa-p/13824973#M4855816</link>
    <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;That query is valid in SQL Anywhere.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Are you sure?&lt;/P&gt;
&lt;P&gt;I'm not that sure because of the different use of correlation names in the UPDATE clause and the FROM clause for table &lt;EM&gt;FGMULTI&lt;/EM&gt; (i.e. without an alias in the former, with an alias in the latter) - cf. the docs:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;If the FROM clause is present, table-name must specify the sole table to be updated, and it must qualify the name in the same way as it appears in the FROM clause. If correlation names are used in the FROM clause, the identical correlation name must be specified as table-name.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;That being said, of course SQL Anywhere is way more flexible than some other DBMSs in that respect (updates on joins), for example MS SQL Server does not allow an alias in the UPDATE clause, AFAIK...&lt;/P&gt;</description>
    <pubDate>Sat, 13 Feb 2016 15:19:21 GMT</pubDate>
    <dc:creator>VolkerBarth</dc:creator>
    <dc:date>2016-02-13T15:19:21Z</dc:date>
    <item>
      <title>Update &amp; Join</title>
      <link>https://community.sap.com/t5/technology-q-a/update-join/qaq-p/13824970</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I keep receiving the error "SQL Command Not Properly Ended".&lt;/P&gt;
&lt;P&gt;I think it has something with my attempt to do with the join.&lt;/P&gt;
&lt;P&gt;UPDATE FGMULTI&lt;/P&gt;
&lt;P&gt;SET NON_CONFORM_ALLOCATABLE = 'Y'&lt;/P&gt;
&lt;P&gt;FROM
      fgmulti as fg
      LEFT OUTER JOIN
      arinvt as ar ON fg.arinvt_id = ar.id&lt;/P&gt;
&lt;P&gt;WHERE
      IN_Date = CurrentDate
      AND 
      ar.Class LIKE 'CP%'
      OR
      ar.Class LIKE 'FG%'
      OR
      ar.Class LIKE 'IN%'
      OR
      ar.Class LIKE 'LA%'
      OR
      ar.Class LIKE 'PK%'&lt;/P&gt;</description>
      <pubDate>Fri, 12 Feb 2016 11:01:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/update-join/qaq-p/13824970</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-02-12T11:01:47Z</dc:date>
    </item>
    <item>
      <title>Re: Update &amp; Join</title>
      <link>https://community.sap.com/t5/technology-q-a/update-join/qaa-p/13824972#M4855815</link>
      <description>&lt;P&gt;Is this a question about MySQL? If it is then this is not the place to ask the question. This forum is for questions about SQL Anywhere.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Feb 2016 11:31:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/update-join/qaa-p/13824972#M4855815</guid>
      <dc:creator>MarkCulp</dc:creator>
      <dc:date>2016-02-12T11:31:04Z</dc:date>
    </item>
    <item>
      <title>Re: Update &amp; Join</title>
      <link>https://community.sap.com/t5/technology-q-a/update-join/qaa-p/13824971#M4855814</link>
      <description>&lt;P&gt;That query is &lt;STRONG&gt;valid in SQL Anywhere&lt;/STRONG&gt;... perhaps you should switch.&lt;/P&gt;
&lt;P&gt;For more reasons to switch from MySQL to SQL Anywhere, see the &lt;STRONG&gt;&lt;A href="http://sqlanywhere.blogspot.ca/2008/03/unpublished-mysql-faq.html"&gt;Unpublished MySQL FAQ&lt;/A&gt;&lt;/STRONG&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Feb 2016 13:24:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/update-join/qaa-p/13824971#M4855814</guid>
      <dc:creator>Breck_Carter</dc:creator>
      <dc:date>2016-02-12T13:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: Update &amp; Join</title>
      <link>https://community.sap.com/t5/technology-q-a/update-join/qaa-p/13824973#M4855816</link>
      <description>&lt;BLOCKQUOTE&gt;
&lt;P&gt;That query is valid in SQL Anywhere.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Are you sure?&lt;/P&gt;
&lt;P&gt;I'm not that sure because of the different use of correlation names in the UPDATE clause and the FROM clause for table &lt;EM&gt;FGMULTI&lt;/EM&gt; (i.e. without an alias in the former, with an alias in the latter) - cf. the docs:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;If the FROM clause is present, table-name must specify the sole table to be updated, and it must qualify the name in the same way as it appears in the FROM clause. If correlation names are used in the FROM clause, the identical correlation name must be specified as table-name.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;That being said, of course SQL Anywhere is way more flexible than some other DBMSs in that respect (updates on joins), for example MS SQL Server does not allow an alias in the UPDATE clause, AFAIK...&lt;/P&gt;</description>
      <pubDate>Sat, 13 Feb 2016 15:19:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/update-join/qaa-p/13824973#M4855816</guid>
      <dc:creator>VolkerBarth</dc:creator>
      <dc:date>2016-02-13T15:19:21Z</dc:date>
    </item>
    <item>
      <title>Re: Update &amp; Join</title>
      <link>https://community.sap.com/t5/technology-q-a/update-join/qaa-p/13824974#M4855817</link>
      <description>&lt;P&gt;I will amend that to read "That query is syntactically valid in SQL Anywhere" since it throws a semantic error "table not found"... and yes, I did test it, to prove that it did not throw the syntactic error "SQL Command Not Properly Ended".&lt;/P&gt;</description>
      <pubDate>Sun, 14 Feb 2016 20:05:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/update-join/qaa-p/13824974#M4855817</guid>
      <dc:creator>Breck_Carter</dc:creator>
      <dc:date>2016-02-14T20:05:57Z</dc:date>
    </item>
  </channel>
</rss>

