On 12/30/2009 1:39 PM, Dan Forward wrote:
The Association tag looks promising, but I am confused by the column
attribute. It wants an ID for the Name, but Names are not first-class data
objects and have no ID. The Association tag seems to be intended for a
one-to-many or many-to-many join. I cou
Hello,
I would like to add support for scala objects to iBATIS 3 for a
project I'm working on, and I have a few questions before I dive in
too deep.
>From what I can tell, this basically entails adding a new wrapper in
org.apache.ibatis.reflection.wrapper that can handle scala's slightly
differen
On 12/30/2009 12:28 AM, vishalj wrote:
Hi,
I am using iBatis for the first time ,but no success yet.This is how my
setup looks like
...
String resource = "com/pg/ibatis/config/Configuration.xml";
Reader reader = Resources.getResourceAsReader(resource);
SqlSessio
On 12/30/2009 8:20 AM, ines DNSCE wrote:
The reason is that the reading of the given méta data has the right DBA.
Thus I reads méta data of another plan (schéma) than I waited.
If I specify the plan for every table, I have no more the problem. On
the other hand it adds me in prefix the name of t
Guy Rouillier-2 wrote:
>
>
> You don't say what version of iBATIS you are using. Since you say you
> are new, so I'm guessing you are using iBATIS 3. You shouldn't need any
> callbacks; from your description, a simple ResultMap should suffice.
> Take a look at the iBATIS 3 User Guide, part
Hi Simone,
I don't know what sort of environment you are developing in but I realized
myself that unless you really have the time to dedicate to editing the
Ibatis source (not really hard but of course it is work intensive) it seems
to be better to keep mapper's simple. I ended up making a priva
Hy guys,
any news about this issue? I just met the case when a mapper needs to
extend an existing one, but mapper methods are not found :(
Thanks in advance!!!
Simone Tripodi
On Fri, Dec 11, 2009 at 11:27 PM, Soks86 wrote:
>
> Sorry for not including this in my previous response.
>
> I also notic
Try this:
Jeff Butler
On Wed, Dec 30, 2009 at 7:20 AM, ines DNSCE wrote:
>
> The reason is that the reading of the given méta data has the right DBA.
> Thus I reads méta data of another plan (schéma) than I waited.
> If I specify the plan for every table, I have no more the problem. On the
Well... I don't know what to tell you. iBATIS isn't reporting an error, and
doesn't often fail silently (if ever). You can try turning on logging and
replace your main method with a unit test that has assertions like
assertNotNull(userProfile);, which is cleaner than letting an NPE occur.
Clinto
The reason is that the reading of the given méta data has the right DBA. Thus I
reads méta data of another plan (schéma) than I waited.
If I specify the plan for every table, I have no more the problem. On the other
hand it adds me in prefix the name of the plan, I must be able to configure it
The Oracle columns are number(1) and number(8). Ibator don't show me warnings.
> From: jeffgbut...@gmail.com
>
> Usually Ibator will ignore a column only if it encounters an
> unsupported data type. Ibator should show a warning if that happens.
>
> Unsupported data typed are fairly common wit
tha db table contains a row with id vakue of '1' which i am trying to query
.And also the same select statement is working fine
Clinton Begin wrote:
>
> The NPE is coming from your main method (profile.getName()). It's not
> finding the profile record. It looks like iBATIS is working, but ther
12 matches
Mail list logo