-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Table names are... partially case-sensitive #24
Comments
good catch! have you also encountered this with other tables? also, have you encountered this in the opposite direction? (i.e. |
I haven't had occasion to do extensive testing of that sort, no, mainly
because I very seldom actually want records straight from a table (as
opposed to a PowerQuery).
…On Wed, Feb 23, 2022, 3:22 PM Charlie Bini ***@***.***> wrote:
good catch!
have you also encountered this with other tables? also, have you
encountered this in the opposite direction? (i.e. table.name is lowercase
but record.tables.name is mixed case)
—
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXMRG3NACWZVXM6KHAVORS3U4U6X5ANCNFSM5PFLEKMA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I just struggled with this issue as well. good The proper case table name returns the expected number of records, but their contents are just "None". |
There's some fairly weird behavior when trying to access tables with non-lowercase names. For example (where ps() returns a PowerSchool() instance):
This appears to be happening because, while PowerSchool smiles tolerantly and returns the results you'd expect, the keys in its response are still all lowercase, as in:
As a result, the second get() call at client.py:243 fails to find a match and returns None (because
self.name
differs from the result's value in case):Whether this should be "fixed" by case-smashing the table name (
self.name.lower()
or so) and/or the keys in the result, or just documented in the future (when there exists documentation), I don't know.The text was updated successfully, but these errors were encountered: