did something (undocumented?) change with SuiteQL

COUNT

? this used to work:

const queryStr = 'SELECT COUNT(*) AS recordcount FROM xxxxx';

, getting recordcount alias, but now comes back as

expr1

it seems? didn't know if this now to be expected, or is better way to phrase query so that Oracle SQL interprets it correctly

How are you executing your query? When do the above using

query.runSuiteQL(queryStr).asMappedResults()

I am getting

recordcount

as the column name, not

expr1

this is running in browser console, but is also occurring in context of REST Api, which is where I noticed originally

@dbarnett I wonder if SuiteQL is using "recordcount" internally, and to resolve the collision, it's ignoring your alias. Have you tried using something else as the alias?

I had not, although just updated the alias to be

xxx

instead, but no luck/same result of

expr1

Weird. It's working for me.

nope 😞 very weird

Very weird, and worrisome, too. because if aliases start breaking, all kinds of other things are likely to break, too.

this is TSDRV account (tried in multiple) so maybe some (hopefully temporary) weirdness going on there and will just resolve itself

Ok, so one more goofy suggestion: Maybe wrap COUNT in parens? ex:

SELECT ( COUNT(*) ) AS recordcount FROM Employee

ohhh weird I just did

COUNT(id)

to try that out and worked 😂

What table were you querying?

Employee same (wrong) behavior with Transaction as well though

Well, I'm glad you have a fix. That is still really strange.

Sorry for bringing this up again... Was the "solution" to the problem to count on id instead of * ? We're experiencing the same "broken alias" behaviour in our production enviroment.

@Thorsten Schmitz yes, use

COUNT(id)

instead

Ok, thanks! Just out of curiosity, did you see any other problems with aliases like simple

SELECT id AS myIdAlias FROM table

?

no, if you scroll up a bit in prior conversation I did try that as a sanity check - a normal field on table did properly alias; seemed to just be an issue when expression was involved

Super strange bug - modifying the

COUNT(*)

to

COUNT(id)

was a fix for me.

Also ran into this. Went and removed any instances of

COUNT(*)

to be sure

is this still a fix? just ran

SELECT COUNT(id) FROM Transaction

... coming back with

expr1

again 😞

@dbarnett It's working for me. In your example, did you forget to add the alias?

@tdietrich ah nevermind lol not enough coffee this friday morning