@ZacBlanco mentioned
Someone in #prestodb asked about it and it is a common issue we've seen pop up. Would probably be good to add a note in the prepared statement section of the documentation with the known limitation & workaround.
Expected Behavior or Use Case
Documentation should be added to address this gap.
Presto Component, Service, or Connector
Documentation.
Possible Implementation
Suggest adding a new page in Troubleshooting, and link to the problem-workaround from PREPARE.
Example Screenshots (if appropriate):
Context
Helps address Issue 13097.