User bio

The first two systems I worked with using InterSystems technology were a PDP-11 running M11+ and a VAX 11/750 running M/VX. Too many years ago to count! 😊
Since then I've used most, if not all, InterSystems products up to IRIS and HealthShare today.
I'm Italian living in Switzerland and I work as Senior Consultant at GAIVOTA consultin SA, we provide professional services for InterSystems and other technologies.
Curiosity: apart from DC, I don't have ANY social account! 😁

Show all
Member since Aug 4, 2017
Posts:
show all 10
Replies:
show all 863
Enrico Parisi · Apr 9 go to post

For example, if you instruct it to extract data where a column value equals “Support,” it may generate a condition like = 'Support' in the SQL query.

However, since the actual returned value is “SUPPORT,” the condition does not match.

Not really, when using the default %String collation (SQLUPPER) the SQL "=" condition is case insensitive, for example:

WHERE name = 'Enrico'
WHERE name = 'ENRICO'
WHERE name = 'enrico'

All match the record/row with my name regardless of the case is stored in the table.

If collation is changed to SQLSTRING, then only exact case will match the condition.

Enrico Parisi · Apr 7 go to post

$$$ThrowOnError(##class(Ens.BusinessService).SendRequestAsync(tServiceConfigName, tRequest))

SendRequestAsync() is an instance method, not a class method, how can this line possibly work?

Certifications & Credly badges:
show all 5
Followers:
show all 12
Stefano M.
Angelo P.
Luis Angel P.
Evgeny S.
Ashok Kumar T.
Sylvain G.
Riccar G.
Following:
Enrico has not followed anybody yet.