Hi there!
I think it's better off making the paging logic yourself in the
application, and then querying only the records you want to show, for
example in oracle you can use the rownum to fetch the data like
select * from
(select rownum row, a.* from tabel1 as a)
where row between 21 and 30
W
Hi Paul,
The difference you were seeing between windows and AIX must be a difference between JDBC drivers. I believe that DB2 V8 is a little bit more forgiving in this area - so maybe that's the difference?
Regardless, this exposes something that needs to change in Abator - because you should
Sorry, I don't know enough about Spring to be able to help you. In my
experience with Struts and tomcat, jboss, and weblogic, DTDs are
looked up automatically in the JARs that are in the WAR/EAR file as
long as the DTD spec in the XML file matches EXACTLY the decl at the
top of the DTD file in the
The new DOCTYPES are on the iBATIS home page in the news section. Please make sure you are using them exactly as specified.
Also, there was an issue related to this problem some time ago (I can't remember exactly which release fixed the issue). If you still have a problem after upgrading to the
Title: Update Statement Error ?
Hi All,
I am getting the following error when calling an Update. I can see UserDTO is passes properly with data. May be declaration is not right ?
Error
com.ibatis.common.jdbc.exception.NestedSQLException:
--- The error occurred in com/ml/camsweb/resourc
Title: Update Statement Error ?
Ali,
It could be because of null value(s) in password
date etc. Check the datatype & acceptable value for fields in db table
vs the dto. Execute the SQL outside ibatis (winsql, plsql etc) with
the values you are passing when this error is occuring. That sho
Another quick-n-dirty way to find these (if you have a unit test) is
to remove columns from the update until it works. The last one you
removed is the problem.
Larry
On 4/26/06, Balaji <[EMAIL PROTECTED]> wrote:
>
> Ali,
>
> It could be because of null value(s) in password date etc. Check the
>
Title: RE: Update Statement Error ?
Hi All,
I ran the update sql outside with the same values and no issues.
I have "null" data values in updates as column allows NULLS for VARCHAR. I think it is giving error on "null" data.
Is there an issue in IBATIS with null data updating in Varchar
Title: RE: Update Statement Error ?
If you are using sybase & jconnect here
is what their error guide says
JZ0SL
Unsupported SQL type _.
Description: The application has declared a parameter to be of a type that
jConnect does not support.
Action: If possible, try declaring the parameter
There is no iBATIS issue with NULL. But in general with nulls, you need to change your mapping to let iBATIS know about the dataype. For example:
first_name = #firstName:VARCHAR#, last_name = #lastName:VARCHAR#, phone = #phone:VARCHAR#, fax = #fax:VARCHAR#, e_mai
Title: Message
Hi
All,
This
declaration worked. Thanks again for your quick response and
support.
Thanks,
Ali
(201)
671-5499
-Original Message-From: Jeff Butler
[mailto:[EMAIL PROTECTED] Sent: Wednesday, April 26, 2006
12:22 PMTo: [email protected]:
Hi, does any one know how to add a new code generator
for iBATIS? I am finishing the first beta version now
and I would like to make it public.
Thanks,
Vladimir.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
h
Hi,
I don't know if this is true,
but i think i've tried that solution before, and when i see the log
generated from the ResultSet, it actually query all the data, and then
selecting only the required record to show..
Yusuf.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTE
Hi, regarding the 'invalid column type' problem, I've tried to reproduce
it :
i made 2 insert statement, one using map as a parameter, another using
simple pojo class :
INSERT INTO EMP ( EMPNO, ENAME, JOB, MGR, HIREDATE, SAL, COMM,
DEPTNO)
VALUES (
#empno:NUMBER#,
The JDBC type specified in the mapping can only be one of the standard JDBC types that are listed in java.sql.Types. Some of the types you are specifying (VARCHAR2, NUMBER) are invalid - and iBATIS will use Types.OTHER
in those cases. This is likely that cause of the problem you are seeing. Swi
The best thing to do is make the tool available publicly somewhere like Sourceforge. You can make an announcement of availability on this list, but please don't use this list to support the tool (Sourceforge would offer a mailing list service). We also have a WIKI page for 3rd party contributions
Oops.. my mistake... actually after reading again the issue in
confluence, i completely missed this line :
"Now you may be asking yourself what are the valid jdbc types. Look no
further they are posted in the Java API documents java.sql.Types"
i never thought about it.. I changed the mappings
17 matches
Mail list logo
