Hi all,
I've been working with ibatis for several years but because version
1.3+ wasn't supporting multiple datasource in the sqlmap I didn't update
since this time:-( I don't have this limitation anymore and I wonder
if the upgrade worth the effort.
I probably have arroud 60 sql maps.
You can use the Ant task to upgrade your sql maps, or just a find/replace. On one project with about 80 result maps I did it with find/replace - it's pretty easy.
The only real issue we had with upgrading that project is that iBATIS 2.x will throw an exception if you execute a queryForObject but
I concure. Please upgrade and let us know if you have any problems.
nathan
On 8/14/06, Jeff Butler [EMAIL PROTECTED] wrote:
You can use the Ant task to upgrade your sql maps, or just a
find/replace. On one project with about 80 result maps I did it
with find/replace - it's pretty easy.
The only
I even *concur* :)On 8/14/06, Nathan Maves [EMAIL PROTECTED] wrote:
I concure. Please upgrade and let us know if you have any problems.
nathan
On 8/14/06, Jeff Butler [EMAIL PROTECTED]
wrote:
You can use the Ant task to upgrade your sql maps, or just a
find/replace. On one project with about 80
YES! CONCURE!!! ;-)David: Are you using JDK 1.4 or greater?Cheers,ClintonOn 8/14/06, Nathan Maves
[EMAIL PROTECTED] wrote:I even *concur* :)
On 8/14/06, Nathan Maves [EMAIL PROTECTED]
wrote:
I concure. Please upgrade and let us know if you have any problems.
nathan
On 8/14/06, Jeff Butler
On Mon, Aug 14, 2006 at 09:38:02AM -0600, Larry Meadors wrote:
The simplest solution is for you to make the setters for the
properties on com.project.Entity.Task not throw NPEs. ;-)
The thing is I don't have methods whch are throwing MPEs. I found such thing
happens when setProperty(int
what version of the jdk are you using?
can you post the sqlmap as well as the set/get method of the property that you are having issues with?
On 8/14/06, Eugeny N Dzhurinsky [EMAIL PROTECTED] wrote:
On Mon, Aug 14, 2006 at 09:38:02AM -0600, Larry Meadors wrote:The simplest solution is for you to
Not really. But here's a quick personal take: * Turn invalid the JDBC 4.0 Ease of Development API by kicking the living snot out of it. * Make laughable the Microsoft DLINQ API. * Bring to the enterprise the ways of Ruby without ActiveRecord.
* Remain a good neighbour to Spring, Hibernate and our
Ahh, yeah, you can't set an int to null, if the values can be null, they have to be Integer instead.LarryOn 8/14/06, Eugeny N Dzhurinsky
[EMAIL PROTECTED] wrote:On Mon, Aug 14, 2006 at 09:38:02AM -0600, Larry Meadors wrote:
The simplest solution is for you to make the setters for theproperties on
Eugeny that is why I asked what jdk you are using. If you can run java 1.5 you will not have these issues.
nathanOn 8/14/06, Larry Meadors [EMAIL PROTECTED] wrote:
Ahh, yeah, you can't set an int to null, if the values can be null, they have to be Integer instead.Larry
On 8/14/06, Eugeny N
Hi,
Thanks for the help! I will then ;-)
I'm using 1.5 so this shouldn`t be a problem.
Maybe another question that you may answer since your know well all the
db stuff. I came to the idea of upgrading ibatis because I tried to
upgrade my postgresql jdbc driver. I get this exception:
hello again,
i'd like to do something like the following,
a 'dynamic where clause':
public ListOdmCustomer search( long groupId, String criterion,
ListString columns )
{
String where = ;
while (existsNext)
{
column = (String) i.next();
where += column + LIKE '% + criterion +
There's no way to do this with Abator generated queries...yet...
Right now with Abator you can only do one LIKE clause in the dynamic where clause.
With the next version of Abator you'll be able to do multiple LIKE clauses or'd together in the dynamic where clause (you'll be able to generate
I am confused..what is an empty number?LarryOn 8/14/06, Reuben Firmin [EMAIL PROTECTED]
wrote:
How do I pass an
empty value into a java.lang.Long field for a sproc? Null is not acceptable on
the sproc side of things, and Ibatis won't take .
My sproc definition
is:
statement ...
I
didn't write the sproc. Don't ask me :D
It is
acceptable in AS400-land - I guess the questionboils down to:what is
the least terrible hack on the DAO/Ibatis side of things?
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Larry
MeadorsSent:
Those crazy iSeries nuts...don't they curse at you for calling it an AS/400?Anyway, I guess I'd try 0, but if that's a valid value (i.e., not the same as empty or null), then I'd try it as a String.
LarryOn 8/14/06, Reuben Firmin [EMAIL PROTECTED] wrote:
I
didn't write the sproc. Don't ask
Well even the iSeries nuts know the difference between a string and a number. :-)
What's the procedure expecting - number or string?
Jeff Butler
On 8/14/06, Larry Meadors [EMAIL PROTECTED] wrote:
Those crazy iSeries nuts...don't they curse at you for calling it an AS/400?Anyway, I guess I'd try
I have a table that looks something like this:
external_maps
Parent externalId type
1 1 1
1 2 1
1 3 1
1 8 2
1
You can set it with the resultSetType attribute of the select element.PS: 2.2.0 is coming out in a few days. Feel free to continue your upgrade efforts, as it will be compatible, but I'd suggest going to production with
2.2.0 (after testing of course).Cheers,ClintonOn 8/14/06, David Gagnon [EMAIL
It might take some trial and error, but you might be able to get it to work.You may need to use groupBy and a second resultMap, even though you're only using primitives. This will aggregate the external ids beneath the unique types. Map the whole thing to a hashmap. Initially this will get you a
20 matches
Mail list logo