You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Migrated issue, originally created by Michael Bayer (@zzzeek)
I think we need a new method on type that's specific to rendering a type for literal SQL. At the moment, a string type on an encoding backend can pass in a bytes into render_literal_value (see test.sql.test_types:EnumTest.test_mock_engine_no_prob using Oracle backend on python3). We're working around this by re-decoding the bytes in the method, but more elaborate bind processor schemes will need to be aware of literal SQL and naturally this should be type-based in any case.
The text was updated successfully, but these errors were encountered:
initial idea is in the ticket_2838 branch at bc5834d6431663ad2a03677af87dd96a8de923e1. we'll move the whole concept of literal bind rendering into the type system.
the String type will also need to determine if encoding is needed here.
Migrated issue, originally created by Michael Bayer (@zzzeek)
I think we need a new method on type that's specific to rendering a type for literal SQL. At the moment, a string type on an encoding backend can pass in a bytes into render_literal_value (see test.sql.test_types:EnumTest.test_mock_engine_no_prob using Oracle backend on python3). We're working around this by re-decoding the bytes in the method, but more elaborate bind processor schemes will need to be aware of literal SQL and naturally this should be type-based in any case.
The text was updated successfully, but these errors were encountered: