Archive
Highlighted

Case Sensitive Columns From SQL

Motivator

When upgrading from 1.1.0 to 1.1.1 DB Connect, I had to change all my fields from being written with capitalization the same as the sql query to all lower case, otherwise none of my fields showed up in the output when queried. For example SELECT Field1,Field2,Field3 from datasource

Then having $Field1$, $Field2$ $Field3$ would return nothing in my template output, but having $field1$, $field2$, $field3$ in my template would output the data correctly, This affected many of my connections and I had to go through them all and lower case them.

Highlighted

Re: Case Sensitive Columns From SQL

Motivator

I guess my question is, was this intended? Do I need worry about upper casing them back to the way they were?

0 Karma
Highlighted

Re: Case Sensitive Columns From SQL

Explorer

I'm seeing this behavior as well. Is there any way to roll this back to the way it behaved before the upgrade? This is adversely affecting self-service use in our org, as users have to rename all capitalized field references in their saved searches.

0 Karma
Highlighted

Re: Case Sensitive Columns From SQL

Engager

I've encountered this too, after install the new version of DBConnect all of my views (which rely on case sensitive camel-case fields) now return 0 results. Very frustrating and time-consuming to resolve!

0 Karma
Highlighted

Re: Case Sensitive Columns From SQL

Motivator

It appears this may have been solved in version 1.1.2:
http://docs.splunk.com/Documentation/DBX/1.1.2/DeployDBX/Releasenotes

Table column names were unexpectedly converted to lower case. (DBX-347)

View solution in original post

0 Karma