Re: CLOBs with Oracle 9i

2005-04-27 Thread Geoff Chiang
As Richard has already said, the 10g drivers should work. If that is not possible or practical in your environment, however, there is a way to create a TypeHandler implementation that handles Oracle clobs using the 9i thin driver and which doesn't suffer from the 4000 character limit issue. The c

Re: CLOBs with Oracle 9i

2005-04-27 Thread Richard Yee
Francisco, You can use the 9i OCI drivers to get around the 4000-char limit. I'd suggest just downloading the 10g drivers. They should work with 9i. -Richard At 05:30 PM 4/27/2005, you wrote: Hello, i am having some trouble with oracle9i in sqlmaps. I was using LONG for a table attribute, but i

Re: CLOBs with Oracle 9i

2005-04-27 Thread Richard Yee
Francisco, There is a 4000 char limit if you use Oracle thin JDBC Drivers prior to 10g. It is a bug in the JDBC driver itself. -Richard At 05:30 PM 4/27/2005, you wrote: Hello, i am having some trouble with oracle9i in sqlmaps. I was using LONG for a table attribute, but it doesn't support being

RE: Is there a way to remove the quotation marks that ibatis inserts when using #[]# on the tag?

2005-04-27 Thread Abeyratne, Sam
Hey Brandon, Thanks for fixing this bug. I checked out a copy of ibatis from SVN and tested with $[]$. It now takes literal values! Awesome! Thanks again! Sam -Original Message- From: Brandon Goodin [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 3:35 PM To: ibatis-user-java@incu

CLOBs with Oracle 9i

2005-04-27 Thread Francisco Leon
Hello, i am having some trouble with oracle9i in sqlmaps. I was using LONG for a table attribute, but it doesn't support being used in WHERE, so i changed it to a CLOB and now sqlmaps can't handle it therefore the attribute is always null. I have read that the latest sqlmaps has a clob handler, b

Re: Mapping Help

2005-04-27 Thread Brandon Goodin
You would have to perform your inserts individually from your Dao class calling insert statements for each table. Start a transaction... perform your insert t_filter insert, perform t_filter_status inserts, perform t_filter_assignment... end transaction. Brandon On 4/27/05, Gregg D Bolinger <[EMA

Mapping Help

2005-04-27 Thread Gregg D Bolinger
I need a bit of help with setting up a mapping file or 2. I have a POJO called Filter. I use this to store options from the user as for search criteria. I have a database that relates to this filter. The problem I am having is I have 2 List properties that are part of Filter. 1 is Status and t

Re: Ibatis property file issue

2005-04-27 Thread Larry Meadors
There really is no such thing as a "relative" URL. If you wanted to, you could specify the path in the properties file like this: sqlMapHome=/usr/local/whatever Then use this in the SqlMapConfig.xml: file://${sqlMapHome}/maps/Active_Agent_Office_View.xml"/> Larry On 4/27/05, Wulf, Andrew <[E

Ibatis property file issue

2005-04-27 Thread Wulf, Andrew
Title: Ibatis property file issue We develop our apps in two environments, Eclipse/IntelliJ for business logic and BEA Weblogic Workshop for the portal UI. The problem is in creating a single iBatis property file that will work in both environments. If I use the classpath for the property fi

Re: debugging sql statements

2005-04-27 Thread Brandon Goodin
DEBUG should do it. On 4/27/05, Jason Punzalan <[EMAIL PROTECTED]> wrote: > is there anyway to output the sql statement before the sql exception is > thrown. i'm getting a syntax exception from oracle but i have no idea what > the sql statement looks like. here's my current log4j.properties file.

Re: Output parameters with optional result set

2005-04-27 Thread David Whipple
Thanks. It is definitely not always the case. We will work around this - I think iBATIS is really nice. I will put this in as a feature request. Thanks, Dave

debugging sql statements

2005-04-27 Thread Jason Punzalan
is there anyway to output the sql statement before the sql exception is thrown. i'm getting a syntax exception from oracle but i have no idea what the sql statement looks like. here's my current  log4j.properties file...i can see the query sent for correct statements though. log4j.rootLogger=ERRO

Re: invalid column type

2005-04-27 Thread Clinton Begin
You don't NEED null value replacements, just the type.  So this would be fine: insert into PRODUCT (PRD_ID, PRD_DESCRIPTION) values (#id:NUMERIC#,#description:VARCHAR#);   This is an Oracle requirement supported by the standard JDBC intereface.  The method signature for setti

Re: invalid column type

2005-04-27 Thread Clinton Begin
Make sure you've specified the JDBC type of *ALL* nullable columns. Oracle requires the type for nullable columns to be specified. Otherwise when you try to set a null value you'll get that invalid column type error. Cheers, clinton On 4/26/05, Jason Punzalan <[EMAIL PROTECTED]> wrote: > thi

Re: invalid column type

2005-04-27 Thread Jason Punzalan
I noticed that when using the same maps with oracle i need to declare the types and null value replacements in my inline parameter. not sure why though...from the dev handbook...     insert into PRODUCT (PRD_ID, PRD_DESCRIPTION) values (#id:NUMERIC:-99#, #description:VARCHAR:NO_ENTRY#);

Re: Output parameters with optional result set

2005-04-27 Thread Clinton Begin
At this time, there's no easy way to do that. If it's an unusual case, just use JDBC for that one proc. If it's the normal case, then you probably won't find iBATIS too helpful at this time. Cheers, Clinton On 4/27/05, David Whipple <[EMAIL PROTECTED]> wrote: > Unfortunately we are not in a pos

Re: Output parameters with optional result set

2005-04-27 Thread David Whipple
Unfortunately we are not in a position to do so - we do not have any control over what we have to call. We are historically a large mainframe shop, and the people who provide the stored procedures think this is a normal behavior. I think in general one should return empty sets of things, instead

Re: invalid column type

2005-04-27 Thread Daniel H. F. e Silva
Hi Jason, According to the stack trace you've posted, i would say that you are facing problems with data type conversions done by your JDBC driver. I guess your 'isFeature' property is a boolean value and your table column 'isFeature' is of another type? If so, i faced this problem before: my ja