TAP ADQL of MPC designations looses string case?

Hi,

Perhaps already known. When I run queries on the mpc_orbits table in the dp2 schema, I get mixed-case results when using a string-based query.

select * from dp2.mpc_orbits AS mpc_orbits WHERE mpc_orbits.packed_primary_provisional_designation = ‘K15KH4Q’

Returns rows matching K15Kh4Q and K15KH4Q [which are two different objects].

Is that expected for an ‘=’ query ?

JJ

Hi JJ,

That’s definitely a surprise to me, but evidently mariadb (which underlies qserv) defaults to a case-insensitive collation for string comparison. The qserv team is testing a configuration change to the table that will make string comparison case-sensitive, and I expect we will be able to roll that out in the next ~week.

Thanks for the report!

-Colin