Return-Path: 
 <dev-return-2114-apmail-ibatis-dev-archive=ibatis.apache.org@ibatis.apache.org>
Delivered-To: apmail-ibatis-dev-archive@www.apache.org
Received: (qmail 65997 invoked from network); 30 Nov 2005 16:58:12 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 30 Nov 2005 16:58:12 -0000
Received: (qmail 51707 invoked by uid 500); 30 Nov 2005 16:58:10 -0000
Delivered-To: apmail-ibatis-dev-archive@ibatis.apache.org
Received: (qmail 51621 invoked by uid 500); 30 Nov 2005 16:58:10 -0000
Mailing-List: contact dev-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ibatis.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ibatis.apache.org>
List-Post: <mailto:dev@ibatis.apache.org>
List-Id: <dev.ibatis.apache.org>
Reply-To: dev@ibatis.apache.org
Delivered-To: mailing list dev@ibatis.apache.org
Received: (qmail 51609 invoked by uid 500); 30 Nov 2005 16:58:09 -0000
Delivered-To: apmail-incubator-ibatis-dev@incubator.apache.org
Received: (qmail 51605 invoked by uid 99); 30 Nov 2005 16:58:08 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Nov 2005 08:58:08 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of Tim.Ding@telus.com designates
 204.174.64.46 as permitted sender)
Received: from [204.174.64.46] (HELO bliksem.nssi.telus.com) (204.174.64.46)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Nov 2005 08:59:33 -0800
Received: from unknown (HELO bcmsg104.corp.ads) (142.174.10.4)
  by bliksem.nssi.telus.com with ESMTP; 30 Nov 2005 16:57:42 +0000
X-SBRS: None
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAQAAA+k=
X-Ironport-AV: i="3.99,196,1131321600";
   d="scan'217,208"; a="342098749:sNHT37702544"
Received: from BCMSG111.corp.ads ([142.174.35.32]) by bcmsg104.corp.ads with
 Microsoft SMTPSVC(6.0.3790.211);
	 Wed, 30 Nov 2005 08:57:42 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [jira] Created: (IBATIS-215) BSF for dynamic queries
Date: Wed, 30 Nov 2005 08:57:42 -0800
Message-ID: <CD7D5DDE91C4E94182D3D284AA9448AA0154D061@BCMSG111.corp.ads>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [jira] Created: (IBATIS-215) BSF for dynamic queries
Thread-Index: AcXgD5XYmq2Ojjk5RhuvZgvF8RzrWgVvfEow
From: "Tim Ding" <Tim.Ding@telus.com>
To: <dev@ibatis.apache.org>,
	"Clinton Begin \(JIRA\)" <ibatis-dev@incubator.apache.org>
X-OriginalArrivalTime: 30 Nov 2005 16:57:42.0315 (UTC)
 FILETIME=[2DAB17B0:01C5F5CF]
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Good Morning, My friends,

Is there Inline Type Declaring for Update in iBatis? I know for =
Insertion that there is something like:

<statement id=3D"insertProduct" parameterClass=3D"product">
  insert into PRODUCT (PRD_ID, PRD_DESCRIPTION)
  values (#id:NUMERIC#, #description:VARCHAR#);
</statement>

But how about for Update case?

Thanks!
Tim Ding

-----Original Message-----
From: Paul Benedict (JIRA) [mailto:ibatis-dev@incubator.apache.org]=20
Sent: Wednesday, November 02, 2005 4:43 PM
To: ibatis-dev@incubator.apache.org
Subject: [jira] Created: (IBATIS-215) BSF for dynamic queries

BSF for dynamic queries
-----------------------

         Key: IBATIS-215
         URL: http://issues.apache.org/jira/browse/IBATIS-215
     Project: iBatis for Java
        Type: New Feature
  Components: SQL Maps =20
    Reporter: Paul Benedict


While the list of tags to form dynamic queries is suitable, they are =
limiting because they stop the "dreamer from dreaming." More complex =
logic cannot be addressed without creating a barrage of new tags.

I propose a new tag called <script> (or something similar) which is =
backed by the Apache Bean Scripting Framework. The parameter map passed =
in to the <statement> should load it into the scripting Interpreter =
object and expose it for the <script> tag so that dynamic Java or =
JavaScript can return
boolean parameters. Obviously there is a performance hit for this and =
the previous tags would be much simpler for common boolean operations, =
but the sky is the limit when it comes to what you can compare inside =
the script.

Example:
<select id=3D"dynamicGetAccountList" =
cacheModel=3D"resultMap=3D"account-result" >
    select * from ACCOUNT
   <script><expression>obj.id !=3D null && obj.id > 0 && =
obj.lastName.startsWith("B")"</expression>
     where ACC_ID =3D #id# and
    ACC_NAME =3D #lastName#
  </script>
  order by ACC_LAST_NAME
</select>

If BSF is not suitable, please look into OGNL which is popular within =
Apache Tapestry and is a very good alternative.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira