Thanks for your response. I don't see how it could adversely affect
other drivers since this behaviour (of sybase) appears to be well within
the JDBC specification. (It's kind of a grey area). I'll try to
whittle together a patch that is well tested in our environment (we are
using 2.3.0.677) an
I'm writing a jar that will be internally distributed, that will use iBatis
on a certain set of tables. My clients might be using JDBC, iBatis or
Hibernate, so I do not want to force them to set up a SqlMapClient. I’d
rather set up one within my jar, and not worry about how the clients will be
a
Hi Bryan,
this or the dev list is the correct place for asking such questions. Could you
please open a jire issue an
attach your patch against the iBATIS trunk to it?
I'm not really sure how your supposed solution will affect other database /
jdbc drivers. Do you think that it
can do any harm?
I know that other iBatis users have had problems in the past (including
myself) when working with Sybase/MSSQL because of the "Done in proc"
results that get sent by stored procedures or triggers. It appears that
most of these issues have been resolved, but there is still room for
error: In Sybas
Something's wrong with the plugin in 3.4. I'm not sure what it is -
but am working on the new ibator plugin in instead. Hopefully soon -
although I have not as much time to work on it as I want to.
Jeff Butler
On Sun, Nov 16, 2008 at 9:01 PM, Rick <[EMAIL PROTECTED]> wrote:
> Thanks for the re
Hopefully I'm just being a newb and missing something simple. It's
been a while since I worked with iBATIS:)...
My column names and pojo names are the same, so typically I don't even
need a result map created to map my properties (I can just map my
resultClass to the query). Where things break dow
