All Apps and Add-ons

DB Connect 3 ignoring column order in SELECT statement

Shtark
Explorer

Since updating to DB Connect v3 columns are being returned in lexicographical order rather than the order specified in the SELECT statement.

E.g. SELECT Plan, ISP, count() now returns ISP, Plan, count(). The order per the SELECT command was correct in v2.

Anyone else experiencing this?

Fields and Table Splunk commands are obviously workarounds for now but we'd prefer not to have to select the order twice.

t183194
Explorer

Yes a fix would be great please, Im having the same issue in V3.

0 Karma

hkosuru
Explorer

Yes, I have 35 columns from the query. Cannot reorder again. Any workarounds for this?

tries
Path Finder

Only workaround idea I have is to use the table command to sort the columns (e.g. | table Plan, ISP, count(*) )

But I agree it would be great if that can get fixed and work as it used to work within v2

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...