The Instructure Community will enter a read-only state on November 22, 2025 as we prepare to migrate to our new Community platform in early December.
Read our blog post for more info about this change.
Found this content helpful? Log in or sign up to leave a like!
I'm working with CD2 in PostgreSQL and I'm noticing that CD2 seems to take an opinionated stance on data types with many columns being user defined (typically enums). For example, `context_type` in `lti_resource_links` is of type `lti_resource_links__context_type`
I'm just curious about the rationale? Mostly because I'm having challenges configuring an AWS Athena PostgreSQL connector and there are data type limitations. Has anyone else run into data type challenges with the CD2 schema?
Thanks,
Jeff
Solved! Go to Solution.
For anyone who finds themselves in this situation, hat tip to my colleague @alison_myers who found that the solution is to use the JDBC connection parameter:
stringtype=unspecified
If you're using Athena Federated Queries with a PostgreSQL database (or JDBC to PostgreSQL generally), this works broadly for user-defined types.
I've been running my target DB in AWS RDS for quite a while now with no issues using the vanilla DAP client. My DB is Postgres and has yet to fail out due to schema updates or invalid datatypes. The only thing I've ever used Athena for was as a PG/Oracle SQL client to run queries.
For anyone who finds themselves in this situation, hat tip to my colleague @alison_myers who found that the solution is to use the JDBC connection parameter:
stringtype=unspecified
If you're using Athena Federated Queries with a PostgreSQL database (or JDBC to PostgreSQL generally), this works broadly for user-defined types.
Community helpTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign inTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign in