Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Rename cardinality N/A to consistent NO_RESULT

See original GitHub issue

Got this unclear error cardinality N/A cannot be requested. Also it looks like there are few other instances in edgecon.pyx. Should everywhere be NO_RESULT as we document in RST files.

Issue Analytics

State:
Created 4 years ago
Comments:9 (9 by maintainers)

Top GitHub Comments

1reaction

tailhookcommented, Jan 16, 2020

Yes, I meant both ResultCardinality and the error message.

But I’m not sure why we might want to turn an exception to return value. We don’t accept cardinality of NO_RESULT from a client, we can only return it in Describe message. So exception is fine here, just need to have a consistent title for this variant everywhere.

1reaction

aeroscommented, Jan 8, 2020

@tailhook I was out of town when I responded to the @ mention, I just got back home earlier today. I should have time to work on it this week and will let you know if I have any questions. Thanks for checking (:

Top Results From Across the Web

DB2 for IBM i: Listing of SQL messages

Array subscripts, TRIM_ARRAY, UNNEST, CARDINALITY, and MAX_CARDINALITY can ... Message Text: Bind process for specified package name and consistency token ...