On Jun 9, 2011, at 12:37 PM, Eric Lemoine wrote: > On Thu, Jun 9, 2011 at 6:28 PM, Michael Bayer <mike...@zzzcomputing.com> > wrote: >> >> >> That's the default adaption provided by TypeEngine.adapt(). Provide your >> own adapt() that does what's needed. For examples see Interval, Enum. > > Ok, I'll take a look at adapt(). Note that our Geometry type isn't > specific to Oracle though.
When you get it going, if you can show us what you're doing, we can create a prototypical version of your type, demonstrating the kind of "add new arguments per dialect" functionality it has, and add it to our test suite, to ensure those usage patterns don't break. SQLAlchemy usually uses distinct type classes per backend to handle backend-specific arguments, so your approach of allowing DB-specific keyword arguments to a single type, which while entirely appropriate in your case, isn't a pattern we test for at the moment. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
