Re: Select from View (as opposed to table) using iBatis

The View exists in DB2, but no table exists with that name. Yes, 42704 is throws if table is not found. I can run the SQL generated SQL by iBatis (that is spit out in Console) in DB2 control center and get successful results. Yes, while table does not exist, the view exist. The error code of 42

Select from View (as opposed to table) using iBatis

I am using iBatis (2.5) with DB2 version 8.x and Spring 2.5. Is there any issue in querying a view (as opposed to table)? It is a very simple select as: select CD from ${jdbc.schema}.V_MY_VIEW org.impl.CodeBean is a simple POJO with

FileNotFoundException: http://www.mybatis.org/dtd/sql-map-config-2.dtd

I am using iBatis version 2 and Spring 2.5 My XML: http://www.ibatis.com/dtd/sql-map-config-2.dtd";> my1.xml looks like: http://ibatis.apache.org/dtd/sql-map-2.dtd"; > When I start the server with the application deployed, I get error as: org

Re: IBATIS 2.3.3, JDK 1.5 - Optimistic locking strategies

Yes, all these posts do answer my question. And, agree with Clinton Begin as he said - "there is no magic there..." -- View this message in context: http://www.nabble.com/IBATIS-2.3.3%2C-JDK-1.5---Optimistic-locking-strategies-tp19867989p19924928.html Sent from the iBATIS - User - Java mailing

Re: IBATIS 2.3.3, JDK 1.5 - Optimistic locking strategies

My fundamental question was: Is there a way to achieve optimistic locking, if the "OldObject" and/or the update timestamp of the old object were NOT available in scope. It seems that the solution in iBATIS requires you to keep the "OldObject" in scope because, the where clause requires you to p

Re: IBATIS 2.3.3, JDK 1.5 - Optimistic locking strategies

My fundamental question was: Is there a way to achieve optimistic locking using timestamp attribute, if the "OldObject" and/or the update timestamp of the old object is available in scope. All the solutions require you to keep the "OldObject" in scope because, the where clause; requires you to

Re: IBATIS 2.3.3, JDK 1.5 - Optimistic locking strategies

I am still looking for answers to my 5 questions. Option1: Caching solution may not solve optimistic locking issue: iBATIS cache model that can be used to cache LRU objects etc. But it still does not solve the issue of optimistic locking. Consider a scenario like below: Mr. X and Mr. Y have a c

IBATIS 2.3.3, JDK 1.5 - Optimistic locking strategies

I would like to explore the strategies for achieving optimistic locking using iBATIS 2.3.3 and JDK 1.5. Following are the constraints: 1. Need to use timestamp column in the database. Cannot use version column in the database, as the current data model does not support version. 2. It will be poss

P6Spy for logging SQL with value using iBatis in JDK 1.5

I have following questions on using P6Spy for logging SQL (along with the values passed in the prepared statement) using iBatis in JDK 1.5. 1. Has anybody used P6Spy in WebSphere 6.1 (JDK 1.5)? 2. Does P6Spy require you to use its own database driver, and replace the standard database driver (DB2

iBATIS 2.3 -Handling Concurrent Update

What are the options for handling concurrent updates in iBATIS 2.3? As Clinton Begin's "iBATIS in Action" book specifies using timestamp, or version number as a column in database table. Is any other strategy being introduced in the newer version of iBATIS? -- View this message in context: http

Re: Avoid resultMap for Selecting multiple columns from multiple tables

Answer is yes. I tested it out. mule_user wrote: > > New to iBatis. > > I want to select two colums from TABLE_1 (e.g., COL_A and COL_B) and two > columns from TABLE_2 (e.g, COL_C and COL_D). These 4 columns (selected > from two separate tables) are attributes in MyObj.ja

Avoid resultMap for Selecting multiple columns from multiple tables

New to iBatis. I want to select two colums from TABLE_1 (e.g., COL_A and COL_B) and two columns from TABLE_2 (e.g, COL_C and COL_D). These 4 columns (selected from two separate tables) are attributes in MyObj.java (e.g attributeA, attributeB, attributeC and attributeD) respectively. My questi

Performance metrics between iBatis and Hibernate 3.2, or 3.x and above

Is any metrics avialble on performance comparisons between iBatis and Hibernate 3.2, or 3.x and above? -- View this message in context: http://www.nabble.com/Performance-metrics-between-iBatis-and-Hibernate-3.2%2C-or-3.x-and-above-tp18893258p18893258.html Sent from the iBATIS - User - Java maili

Re: Doing Insert, Record not getting committed, no exception is thrown

Found answer to my own question. I forgot enclosed it inside the transaction boundary. It works now. mule_user wrote: > > New to iBatis. Using 2.3.3.720 with Spring 2.5. > > Even though I have access rights for inserts in that table for using the > datasource (user id, passw

Doing Insert, Record not getting committed, no exception is thrown

New to iBatis. Using 2.3.3.720 with Spring 2.5. Even though I have access rights for inserts in that table for using the datasource (user id, password etc.), I do not see the record getting committed. I can successfully do Select on that table using the same datasource. As such, I know that co

Hibernate 3.2 Native SQL versus iBATIS

Will it be possible to provide some pros and cons for the questions below: 1. If I were to use Hibernate 3.2 with Native SQL in several places of the project (because the database is complex and I do not have control over it as a Java developer), am I better off using iBATIS instead? 2. Will it be