Hm... I noticed that SQLTemplate doesn't even set the jdbc type of it's column descriptors... (at least, not in 2.x cayenne...) Should it? There's probably not enough information in #result to guess the type, but maybe a little later in the process, those value could be initialized from the query metadata? Just wondering, since it throws a kink into extended type conversion. (For example, the Enum type conversion fails when using sqltemplate and numeric-based columns because the type is Types.NULL (0), and so it tries do to an Enum.valueOf("string") call, which will fail since the "string" is a number...

Certainly, the individual types can be adjusted to examine the result set metadata, rather than the type argument passed to it.
But that seems like the wrong place to fix this. Thoughts?

Robert

Reply via email to