On 09/28/2016 06:48 PM, Seth P wrote:
On Wednesday, September 28, 2016 at 5:43:04 PM UTC-4, Mike Bayer wrote:
looks incredibly difficult. I'm not really about to have the
resources
to work with a type that awkward anytime soon, unfortunately. If it
could be made to be a drop-in for 1.1's ARRAY feature, that would be
helpful but it at least needs bound parameter support to be solid.
Would it be possible to add read-only support? It looks like cx_Oracle
returns selected varray values in a pretty straightforward form.
That would still be very useful (at least in my case, where I would be
populating the database using SQL*Loader anyway).
you can add your own types to do these things also, especially
read-only, just make any subclass of UserDefinedType and apply whatever
result-row handling is needed for how cx_Oracle is returning the data.
The hard part about types is the elaborate expression support (e.g. like
JSON foo ->> bar vs. foo -> bar in PG for example). Reading and
writing a value is not that hard and especially if the type is just
specific to what you need right now, you don't have the burden of making
sure your type works for all versions / flags / settings of Oracle /
cx_Oracle etc.
--
You received this message because you are subscribed to the Google
Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
