Re: Oracle v$session and iBatis

2009-04-29 Thread Nathan Maves
wow I could take this places, but this is a public list :) On Wed, Apr 29, 2009 at 10:34 AM, Larry Meadors wrote: > On Wed, Apr 29, 2009 at 9:20 AM, Clinton Begin > wrote: > > Larry's cheaper though, if you want to hire him. ;-) > > Not much, but I am more fun to be around. :-D > > Larry >

Re: Using #PARAM# constructions within $DYNAMICSQL$

2009-04-29 Thread DelGurth
On Wed, Apr 29, 2009 at 4:58 PM, Jason King wrote: > Is there some reason you can't use the dynamic where clause feature in > iBatis. > > This is an example stolen directly from Clinton's book. > > > resultClass="Category"> > > SELECT * > > FROM category > > > > > > parentCategoryId IS NULL > >

Re: Oracle v$session and iBatis

2009-04-29 Thread Larry Meadors
On Wed, Apr 29, 2009 at 9:20 AM, Clinton Begin wrote: >  Larry's cheaper though, if you want to hire him.  ;-) Not much, but I am more fun to be around. :-D Larry

Re: Oracle v$session and iBatis

2009-04-29 Thread Clinton Begin
In my opinion, this was more of an Oracle question than an iBATIS question. iBATIS SimpleDataSource doesn't do anything special. It opens and closes connections based on how many you tell it to keep alive, using the driver you specify. It has no idea what a v$session view is, nor do I. The driv

Re: newbie trouble grokking error message

2009-04-29 Thread Sean Mitchell
On Wed, Apr 29, 2009 at 9:46 AM, Nathan Maves wrote: > This really does look like a mapping issue.  Please include the source code > of the bean and the map that you are using. As I'm new to this company and they are a bit uptight about some things, I'm not sure that I can do that just yet. Wil

Re: Using #PARAM# constructions within $DYNAMICSQL$

2009-04-29 Thread Jason King
Is there some reason you can't use the dynamic where clause feature in iBatis. This is an example stolen directly from Clinton's book. SELECT * FROM category parentCategoryId IS NULL parentCategoryId=#parentCategoryId# Doing dynamic

Re: newbie trouble grokking error message

2009-04-29 Thread Nathan Maves
This really does look like a mapping issue. Please include the source code of the bean and the map that you are using. On Wed, Apr 29, 2009 at 7:31 AM, Sean Mitchell wrote: > On Tue, Apr 28, 2009 at 5:52 PM, Nathan Maves > wrote: > > > Welcome to ibatis! > > Thanks... it's a very interesting

Re: newbie trouble grokking error message

2009-04-29 Thread Sean Mitchell
On Wed, Apr 29, 2009 at 6:51 AM, Burke.Kevin wrote: > Check you bean class.  Are your setters public and ok? Make sure you are > mapping to compatible data types from the database back to your bean. If > they cannot be converted implicitly, define a handler in the ibatis SQL > map XML to convert

Re: newbie trouble grokking error message

2009-04-29 Thread Sean Mitchell
On Tue, Apr 28, 2009 at 5:52 PM, Nathan Maves wrote: > Welcome to ibatis! Thanks... it's a very interesting project, not sure how it escaped my notice before. A very nice middle ground between Hibernate and DBUtils. > Could you give us a little more information like what DB you are using? what

Re: Oracle v$session and iBatis

2009-04-29 Thread DelGurth
I'm just wondering, how exactly are are monitoring the connections using v$session? Since 27/28 sessions already seems to be way more then what you configured: Do you filter for the user that you configured and checking the active/inactive status of the session? Wessel On Wed, Apr 29, 2009 at 1

Re: Using #PARAM# constructions within $DYNAMICSQL$

2009-04-29 Thread DelGurth
On Wed, Apr 29, 2009 at 2:44 PM, Chris O'Connell wrote: > I sympathize with your problem.  Perhaps you could just build a set of sql > includes, each of which is the correct sql for a particular use case.  Then, > rather than building the sql string in your code, you instead just pass a > paramete

Re: Using #PARAM# constructions within $DYNAMICSQL$

2009-04-29 Thread Chris O'Connell
I sympathize with your problem. Perhaps you could just build a set of sql includes, each of which is the correct sql for a particular use case. Then, rather than building the sql string in your code, you instead just pass a parameter into iBatis that it can use to determine which is the correct s

Re: Oracle v$session and iBatis

2009-04-29 Thread Larry Meadors
Heh, welcome to Open Source Software. We all have jobs, too. Feel free to contact any of us for freelance work. I'll happily drop all that I'm doing to help you with your app if the rate's high enough. :-D Larry On Wed, Apr 29, 2009 at 5:18 AM, Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 wr

Re: Oracle v$session and iBatis

2009-04-29 Thread Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2
Hey, thanks for the TONS of helpful replies I got to this question! It's a good thing this wasn't to solve an enterprise question or anything. Oh, wait...it was. Signing off... > Oracle v$session and iBatis Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 Tue

RE: newbie trouble grokking error message

2009-04-29 Thread Burke.Kevin
Hi Sean, Check you bean class. Are your setters public and ok? Make sure you are mapping to compatible data types from the database back to your bean. If they cannot be converted implicitly, define a handler in the ibatis SQL map XML to convert to your bean attribute's type. Kevin -Origin

Re: Using #PARAM# constructions within $DYNAMICSQL$

2009-04-29 Thread DelGurth
On Wed, Apr 29, 2009 at 5:30 AM, Nathan Maves wrote: > I have not tried this but I don't see why it would not work. > > > SELECT * FROM person >  WHERE person.lastname LIKE '%'||#lastname#||'%' > > the || is the concat operator for oracle.  it might be something else in > another vendor Probably