On Fri, Aug 05, 2011 at 12:34:47AM -0700, SiGe wrote: > In commit 4893170da20eee28c016408a0f72f1996343a048, there has been a > new method type_cast in quoting which is used to prepare sql- > statements, before that, columns where asked to *quote* their own > value as in > https://github.com/rails/rails/commit/a0d4c8d1bf2198608e2e319ff833560f88d20855#activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb, > > This has broken almost all GIS gems that define their own *columns*, > where should I ask if this was intended? since this can easily be > fixed and made backward compatible by overriding the *else* in > type_cast.
Yes, this change was intentional for supporting prepared statements. We could make it backwards compatible. But this is a completely new feature, so I'm not sure what that means. Could you tell us what you're trying to do, and maybe there is a better, more future proof way to do it? -- Aaron Patterson http://tenderlovemaking.com/
pgpwpJMF0KHiU.pgp
Description: PGP signature
