<?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: DB Connect 3 ignoring column order in SELECT statement in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-3-ignoring-column-order-in-SELECT-statement/m-p/343378#M41509</link>
    <description>&lt;P&gt;Yes a fix would be great please, Im having the same issue in V3. &lt;/P&gt;</description>
    <pubDate>Thu, 07 Sep 2017 02:00:46 GMT</pubDate>
    <dc:creator>t183194</dc:creator>
    <dc:date>2017-09-07T02:00:46Z</dc:date>
    <item>
      <title>DB Connect 3 ignoring column order in SELECT statement</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-3-ignoring-column-order-in-SELECT-statement/m-p/343375#M41506</link>
      <description>&lt;P&gt;Since updating to DB Connect v3 columns are being returned in lexicographical order rather than the order specified in the SELECT statement.&lt;/P&gt;

&lt;P&gt;E.g. &lt;CODE&gt;SELECT Plan, ISP, count(&lt;EM&gt;)&lt;/EM&gt;&lt;/CODE&gt;&lt;EM&gt; now returns ISP, Plan, count(&lt;/EM&gt;). The order per the SELECT command was correct in v2.&lt;/P&gt;

&lt;P&gt;Anyone else experiencing this?&lt;/P&gt;

&lt;P&gt;Fields and Table Splunk commands are obviously workarounds for now but we'd prefer not to have to select the order twice.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2017 00:19:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-3-ignoring-column-order-in-SELECT-statement/m-p/343375#M41506</guid>
      <dc:creator>Shtark</dc:creator>
      <dc:date>2017-03-09T00:19:39Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect 3 ignoring column order in SELECT statement</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-3-ignoring-column-order-in-SELECT-statement/m-p/343376#M41507</link>
      <description>&lt;P&gt;Yes, I have 35 columns from the query.  Cannot reorder again. Any workarounds for this?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2017 14:53:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-3-ignoring-column-order-in-SELECT-statement/m-p/343376#M41507</guid>
      <dc:creator>hkosuru</dc:creator>
      <dc:date>2017-03-16T14:53:05Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect 3 ignoring column order in SELECT statement</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-3-ignoring-column-order-in-SELECT-statement/m-p/343377#M41508</link>
      <description>&lt;P&gt;Only workaround idea I have is to use the table command to sort the columns (e.g. | table Plan, ISP, count(*) )&lt;/P&gt;

&lt;P&gt;But I agree it would be great if that can get fixed and work as it used to work within v2&lt;/P&gt;</description>
      <pubDate>Tue, 02 May 2017 09:20:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-3-ignoring-column-order-in-SELECT-statement/m-p/343377#M41508</guid>
      <dc:creator>tries</dc:creator>
      <dc:date>2017-05-02T09:20:43Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect 3 ignoring column order in SELECT statement</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-3-ignoring-column-order-in-SELECT-statement/m-p/343378#M41509</link>
      <description>&lt;P&gt;Yes a fix would be great please, Im having the same issue in V3. &lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 02:00:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-3-ignoring-column-order-in-SELECT-statement/m-p/343378#M41509</guid>
      <dc:creator>t183194</dc:creator>
      <dc:date>2017-09-07T02:00:46Z</dc:date>
    </item>
  </channel>
</rss>

