ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krishnamoorthi, Sruthi (Raytheon)" <Sruthi.Krishnamoor...@USPTO.GOV>
Subject IBATIS CHAR FIELD NULL VALUES- Urgent help required
Date Fri, 02 Jun 2006 16:41:42 GMT
I have a char field which carries null value. 
The samething with varchar field also.
when I pass null values it was throwing sql exception as incompatible column types. Then for
varchar field i add #centerNo:VARCHAR# and same for DAte field  #priorityDt:DATE#.
When I did same for CHAR #parentPatentNo:CHAR# I got error that inserted value too large for
a column
Then I tried 
#parentPatentNo:CHAR(10)#
Now it says incompatable type column.


<insert id="PatentedCaseTblInsert" parameterClass="PatentedCase">
INSERT INTO PATENTED_CASE (PC_PATENT_NO,PATENT_APPLICATION_NO,FILING_DT, PATENT_ISSUE_DT,
INVENTION_TITLE_TX, TECHNOLOGY_CENTER_NO, APPLICATION_PRIORITY_DT, REISSUE_PARENT_PATENT_NO,
INVENTOR_QT, LAST_MODIFIED_USER_ID,LAST_MODIFIED_TS, ART_UNIT_NO)
VALUES(#patentNo#, #patentApplNo#, #filingDt#, #issueDt#, #title#, #centerNo:VARCHAR#, #priorityDt:DATE#,
#parentPatentNo:CHAR(10)#, #inventorQt#, #lastModifiedUserId#, sysdate, #artUnitNo#)
</insert> 


Could you please provide me a solution very urgently.

Thanks,
Sruthi Krishnamoorthi
703-562-9732(Work)
537 A - (Raytheon) Location 


-----Original Message-----
From: Morone, Bill [mailto:Morone.Bill@pennmutual.com]
Sent: Friday, June 02, 2006 11:20 AM
To: user-java@ibatis.apache.org; lmeadors@apache.org
Subject: RE: When returning mutiple objects and transforming "directly
to xml


Larry,

I will take a better look at the source when I have the time. We can talk. Thanks.

I had to tell my manager about the change in stance regarding the xml moving forward. She
was not happy (I sold her on the xml instead of having java value objects  --get rid of a
layer -- it is only a semantic difference between a java value object and an xml one, right?).

Anyway. Onward 

-----Original Message-----
From: larry.meadors@gmail.com [mailto:larry.meadors@gmail.com]On Behalf
Of Larry Meadors
Sent: Friday, June 02, 2006 10:56 AM
To: user-java@ibatis.apache.org
Subject: Re: When returning mutiple objects and transforming "directly
to xml


I can help you build a row handler to do the transformation if you
need some help (though I suspect you won't), just contact me off-list,
and we can work on it - shouldn't take more than a few minutes to
"rough it in", then you can refine it.

Larry


On 6/2/06, Morone, Bill <Morone.Bill@pennmutual.com> wrote:
>
>
> Gentlemen:
>
> I do thank you and believe you have a fine thing going. Like I said I
> created a very clean little design that basically uses the xml objects
> emitted by iBATIS and transforms them anyway you want (great for little
> docs). I'd like to see stuff move a little forward -- I'll help!!!
>
>
> Bill
>
>
>
>
> -----Original Message-----
> From: Clinton Begin [mailto:clinton.begin@gmail.com]
> Sent: Friday, June 02, 2006 9:45 AM
> To: user-java@ibatis.apache.org
> Subject: Re: When returning mutiple objects and transforming "directly to
> xml
>
>
> Hi Bill,
>
> It will probably go away in version 3.0.  We'd never remove a feature from
> the current major version.  It will continue to be supported in 2.0.
>
> In it's place we'll likely either suggest or build-in second stage xml
> support, for turning classes, beans and maps into XML.  That will allow you
> to map them to domain objects AND convert them to XML.  Plus, there are
> already a number of XML libraries that support exactly that.  The current
> implementation creates too much complexity in the implementation, yet offers
> little additonal value over the formerly described approach.
>
> Don't worry though, we'll always help you upgrade.  Even if it doesn't exist
> in 3.0, we'll have a suggested upgrade path that shouldn't leave you
> floundering.
>
> Cheers,
> Clinton
>
>
>
>
> On 6/2/06, Morone, Bill <Morone.Bill@pennmutual.com> wrote:
> > Larry,
> >
> > Really? I think it bears great merit. I little expansion would make it
> really practical. In fact hearing of its departure has me a little worried.
> >
> > Does this mean the resultClass="xml" is going away?
> >
> > I created a little (restlet front-end) framework that translates the xml
> output for web services. I extended ArrayList to deal with the
> "non-webformedness" of the queryForObject "list of little docs" situation
> and it works great.
> >
> > Our system is scheduled to go into production in October -- what are the
> future plans for the xml stuff -- I assume we'll have to subclass to extend.
> Will your superclass stuff stay the same?
> >
> > Bill Morone
> >
> >
> > -----Original Message-----
> > From: larry.meadors@gmail.com [mailto:larry.meadors@gmail.com]On Behalf
> > Of Larry Meadors
> > Sent: Thursday, June 01, 2006 4:45 PM
> > To: user-java@ibatis.apache.org
> > Subject: Re: When returning mutiple objects and transforming "directly
> > to xml
> >
> >
> > On 6/1/06, Morone, Bill <Morone.Bill@pennmutual.com> wrote:
> > > Coming soon, right?
> >
> > On the contrary, going away.
> >
> > I'd suggest processing the results of the query manually to create XML
> > with a row handler if you really need to create xml results.
> >
> > Larry
> > This message, including any attachments, is intended only for the
> recipient(s)
> > named above. It may contain confidential and privileged information. If
> you have
> > received this communication in error, please notify the sender immediately
> and
> > destroy or delete the original message. Also, please be aware that if you
> are not
> > the intended recipient, any review, disclosure, copying, distribution or
> any
> > action or reliance based on this message is prohibited by law.
> >
> >
>
>
>  This message, including any attachments, is intended only for the
> recipient(s)
> named above. It may contain confidential and privileged information. If you
> have
> received this communication in error, please notify the sender immediately
> and
> destroy or delete the original message. Also, please be aware that if you
> are not
> the intended recipient, any review, disclosure, copying, distribution or any
> action or reliance based on this message is prohibited by law.
>
>
>
This message, including any attachments, is intended only for the recipient(s) 
named above. It may contain confidential and privileged information. If you have 
received this communication in error, please notify the sender immediately and 
destroy or delete the original message. Also, please be aware that if you are not 
the intended recipient, any review, disclosure, copying, distribution or any 
action or reliance based on this message is prohibited by law.  





Mime
View raw message