Re: SqlSession.close() without committing

There never has and most likely never will be an ibatis "specification". Larry On Tuesday, April 6, 2010, cowwoc wrote: > > > Yes, iBATIS will rollback the connection if it deems it necessary.  The only > time you might need to call rollback explicitly is if you have a "select" > that actually

Re: SqlSession.close() without committing

Then you might be happier with a spec like JPA. Although I'd warn that such specs are rarely implemented consistently. This is what has killed J2EE vs. the alternatives. Look at the history: * CMP - Spec. Dead, along with all implementations. * EJB - Spec. Dead. Spring killed it -- not a sp

Re: "JDBC requires that the JdbcType must be specified for all nullable parameters"

Yes, that can be reworded and more information is likely possible. Can you file a Jira ticket for this? Clinton On Tue, Apr 6, 2010 at 10:09 PM, cowwoc wrote: > Hi, > >I am getting an error message: > >"JDBC requires that the JdbcType must be specified for all nullable > parameters [..

Re: "JDBC requires that the JdbcType must be specified for all nullable parameters"

Null parameters are allowed, so we can't fail upon them. To maintain compatibility with string based calls against map parameters, we don't distinguish between a null keyed entry in the map and no keyed entry at all. I'd be willing to consider this change, but it's one of those things that has al

Re: SqlSession.close() without committing

Hello: Maybe some guys can dig into the source codes of iBatis and write a book called 'Inside iBatis3'. Who want to write it?I want to buy it. :) By the way,I like JSF. 陈抒 Best regards http://blog.csdn.net/sheismylife On Wed, Apr 7, 2010 at 9:50 PM, Clinton Begin wrote: > Then you mig

Dynamic table replacement possible in iBatis3 ?

Hi All, I was wondering if this is possible with iBatis 3: select count(*) from ${tableName} The problem is that the string ${tableName} is not replaced by the parameter, leadin to a 'select count(*) from null' at runtime. Am I doing something wrong here or is this feature not yet implemet

Re: SqlSession.close() without committing

Clinton, I'm not looking for a specification in that sense of the word :) I meant something along the lines of Design by Contract: http://en.wikipedia.org/wiki/Design_by_contract If my code depends on iBatis and upgrading to a newer version breaks my code then how do we establish whe

Re: Dynamic table replacement possible in iBatis3 ?

this still works in IB3. Give us more of your code to figure out where the issue really is. Show us the full sqlmap/annotation as well as the calling method. N On Wed, Apr 7, 2010 at 8:46 AM, Joram Barrez wrote: > Hi All, > > I was wondering if this is possible with iBatis 3: > > >    select c

Re: SqlSession.close() without committing

One thing I'd have liked to see is an indicator of which packages are intended as API packages for public consumption, and which packages are implementation. The idea being that I'd like to minimise dependencies on 'private' API. There're a few incentives to do that: * making sure you're using a

RE: SqlSession.close() without committing

Hey Clinton, You've got volunteers coming out of the woodwork ;-) -Original Message- From: Martin Ellis [mailto:[email protected]] Sent: Wednesday, April 07, 2010 11:43 AM To: [email protected] Subject: Re: SqlSession.close() without committing One thing I'd have liked to see

Re: SqlSession.close() without committing

Unit Tests! On Wed, Apr 7, 2010 at 9:53 AM, cowwoc wrote: > Clinton, > > I'm not looking for a specification in that sense of the word :) I > meant something along the lines of Design by Contract: > http://en.wikipedia.org/wiki/Design_by_contract > > If my code depends on iBatis and upg

Re: SqlSession.close() without committing

>> One thing I'd have liked to see is an indicator of which packages are >> intended as API packages for public consumption, and which packages >> are implementation. iBATIS 2.0 did that quite explicitly. It literally had a package separation between public and internal APIs. Unfortunately, like

Re: SqlSession.close() without committing

On 4/7/2010 9:50 AM, Clinton Begin wrote: This is what has killed J2EE vs. the alternatives. Look at the history: Not to start a flame war, but ... * CMP - Spec. Dead, along with all implementations. * EJB - Spec. Dead. Spring killed it -- not a spec. EJB3 is very much alive. The sp

object no longer exists

Hi, I am caching a query with ibatis. The query is as below SELECT ulog.user_id user_id, user_name( ulog.user_id) user_name FROM user_login ulog WHERE user_type_code = 'E' AND

Re: SqlSession.close() without committing

On Wed, Apr 7, 2010 at 11:04 AM, Clinton Begin wrote: > There was once a man named Larry, > Who felt my code was scary, > For the code at which he balked, > He wrote JavaDocs, > And left the community merry. LOL! Should I be worried that you're writing poetry about me? :-D I guess I'll just be g

Re: SqlSession.close() without committing

Rick, I don't think making facetious comments is likely to help, particularly when talking about people who already submit patches, and submit feedback on betas. Martin On 7 April 2010 17:46, Rick.Wellman wrote: > Hey Clinton, > You've got volunteers coming out of the woodwork ;-) > > -Ori

FW: object no longer exists

Just resending it, as I got a failure notice Thanks Vinaya From: Vinaya Tirikkovalluru [mailto:[email protected]] Sent: Wednesday, April 07, 2010 1:11 PM To: [email protected] Subject: object no longer exists Hi, I am cac

Re: SqlSession.close() without committing

I agree, EJB 3 looks very good. But my point was that the first two iterations of the spec didn't help. And if anything, the non-spec driven Spring framework drove EJB 3 to be what it is today. Clinton On Wed, Apr 7, 2010 at 11:06 AM, Guy Rouillier wrote: > On 4/7/2010 9:50 AM, Clinton Begin w

Re: [IBatis3-beta10] nested results for collection

Hi Clinton Basically what I am seeing is the nested select is not getting executed. To make it simpler, I created a simple prototype. I know in this example I don't need to create a separate select, but wondering why its not working. Here are the details POJOs public class Car {

Re: [IBatis3-beta10] nested results for collection

Ah, found it. The column attribute was missing from Collection. Added that and it worked. ofType="Parts" select="getCarPartInfo"/> 2010-04-07 11:38:47,254 DEBUG [iBatisImplTest] Car id 1 name Audi 2010-04-07 11:38:47,255 DEBUG [iBatisImplTest] car Part iterator is not null 3 2010-04-07 1

Re: SqlSession.close() without committing

Martin, I appreciate your point, but Rick's is valid to. Sometimes it's easy to get the general feeling that people think iBATIS or the ASF is a business, and they expect our project to work for them. However, this is not a business. I don't make any money from iBATIS (as in ZERO). I've contri

Re: FW: object no longer exists

This is a sql exception from oracle. This does not look like it has anything to do with ibatis. On Wed, Apr 7, 2010 at 11:52 AM, Vinaya Tirikkovalluru wrote: > Just resending it, as I got a failure notice > > > > Thanks > Vinaya > > > > > > From: Vinaya Tirikkova

Re: [IBatis3-beta10] nested results for collection

Weird that an error was not thrown in that case... I'll have a look to see why this condition would go ignored. Thanks for tracking the defect down. If you get a chance, copy this message into a Jira defect. Clinton On Wed, Apr 7, 2010 at 12:41 PM, Viv Kapadekar wrote: > Ah, found it. The colu

Re: [IBatis3-beta10] nested results for collection

Sure, I can. BTW in the User Guide on Page 38 I see this Nested Select for Collection First, let’s look at using a nested select to load the Posts for the Blog. SELECT * FROM BLOG WHERE ID = #{id} SELECT * FROM POST WHERE BLOG_ID = #{id} Should it be Post instead? Thanks --V On Ap

Re: Dynamic table replacement possible in iBatis3 ?

In iBATIS 2, you would use ${value}. Maybe this still holds for version 3? Niels On 7 April 2010 16:46, Joram Barrez wrote: > Hi All, > > I was wondering if this is possible with iBatis 3: > > >select count(*) from ${tableName} > > > The problem is that the string ${tableName} is not repl

Re: Dynamic table replacement possible in iBatis3 ?

The format did change, here is the new format: /* contents.Content.selectCountBySourceKey */ SELECT COUNT(*) FROMcontents WHERE source_key = #{value} François On Apr 7, 2010, at 5:54 PM, Niels Beekman wro

Re: "JDBC requires that the JdbcType must be specified for all nullable parameters"

Done: https://issues.apache.org/jira/browse/IBATIS-772 Thanks, Gili On 07/04/2010 9:54 AM, Clinton Begin wrote: Null parameters are allowed, so we can't fail upon them. To maintain compatibility with string based calls against map parameters, we don't distinguish between a null keyed ent

Re: "JDBC requires that the JdbcType must be specified for all nullable parameters"

Done: https://issues.apache.org/jira/browse/IBATIS-771 Gili On 07/04/2010 9:52 AM, Clinton Begin wrote: Yes, that can be reworded and more information is likely possible. Can you file a Jira ticket for this? Clinton On Tue, Apr 6, 2010 at 10:09 PM, cowwoc

Re: SqlSession.close() without committing

Clinton and Rick, I do not think that iBatis is a business, nor am I attempting to make demands as to how you should run your project. I've learned a long time ago that no amount of pressure will work with open-source projects. Good projects are few and far between so I appreciate what you