Character/Numeric Issues Query Entity Rules

RE: Character/Numeric Issues Query Entity Rules

PhilB — Fri, 02 Sep 2016 19:31:06 GMT

I think this is probably more of a database question than query entity, as ultimately your query entity will eventually end up as a SQL query. Try running the following one at a time, and I think you'll have the answer to your question:

select 1 !=1; -- should be 0 (ie false)
select 8 = 8; -- should be 1 (ie true)
select '8' = 8; -- should be 1 (ie true)

Out of interest, are you converting the primary key field to text, and/or doing the same with a field that you use as a way of finding rows? If so you may want to consider the effects that converting to text will have on the table indexes, as well as how you're going to ensure that column is unique.

RE: Character/Numeric Issues Query Entity Rules

georgej — Fri, 02 Sep 2016 19:29:24 GMT

Certainly, but we would like to have more insight into the behavior highlighted in the question. How APPIAN is interpreting the data type ,though it is defined as numeric but is accepting both text/numeric

RE: Character/Numeric Issues Query Entity Rules

aayusha — Fri, 02 Sep 2016 19:27:43 GMT

I should say It is a good practice to change and keep this consistent.

RE: Character/Numeric Issues Query Entity Rules

aayusha — Fri, 02 Sep 2016 19:26:58 GMT

As far as I have seen till now, it should not create any issues as you are converting a integer column to text but ideally all the dependencies should be changed.