You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-cs@ibatis.apache.org by Christopher DeGuise <ch...@be-pragmatic.com> on 2007/11/06 19:16:10 UTC
Problems extending statements from another map file.
Hi,
I have found that I can not create a SQL statement when extending from a SQL
statement from another map file. The problem appears to be in the method
"ProcesSqlStatement" in class "DomSqlMapBuilder". The method only looks
within the current map file for the extended statement. Has anyone else
noticed this problem before or am I the first to try extending across maps?
I looked at fixing it but it gets a bit more complicated with parameter
maps, etc. My use case is really just a raw select that acts as the base for
all queries that expect to return the particular result map.
Thanks,
Chris
Re: Problems extending statements from another map file.
Posted by Christopher DeGuise <ch...@be-pragmatic.com>.
Okay, that sounds reasonable and I can live with it. When I looked at maybe
patching it myself it seemed like it might be a bit tricky in the current
architecture.
Thanks,
Chris
On 11/6/07, Gilles Bayon <ib...@gmail.com> wrote:
>
> For now, you can only use extends for statement in the same mapping file.
> This limitation will be removed in the DataMapper V2 version with a new
> configuration engine.
> This limitation does not apply for parameterMap. The extends parameterMap
> must have been already resolve in a previous mapping file or be present in
> the same mapping file
> --
> Cheers,
> Gilles
>
> <a href="http://www.amazon.com/gp/registry/6JCP7AORB0LE">Wish List</a>
--
Christopher DeGuise
Pragmatic Technologies, Inc.
802.881.8287
Re: Problems extending statements from another map file.
Posted by Gilles Bayon <ib...@gmail.com>.
For now, you can only use extends for statement in the same mapping file.
This limitation will be removed in the DataMapper V2 version with a new
configuration engine.
This limitation does not apply for parameterMap. The extends parameterMap
must have been already resolve in a previous mapping file or be present in
the same mapping file
--
Cheers,
Gilles
<a href="http://www.amazon.com/gp/registry/6JCP7AORB0LE">Wish List</a>
RE: Problems extending statements from another map file.
Posted by "Clough, Samuel (USPC.PRG.Atlanta)" <Sa...@princetonrg.com>.
Are you using the proper namespace prefix when trying to extend a
statement?
From: Christopher DeGuise [mailto:christopher.deguise@be-pragmatic.com]
Sent: Tuesday, November 06, 2007 1:16 PM
To: user-cs@ibatis.apache.org
Subject: Problems extending statements from another map file.
Hi,
I have found that I can not create a SQL statement when extending from a
SQL statement from another map file. The problem appears to be in the
method "ProcesSqlStatement" in class "DomSqlMapBuilder". The method only
looks within the current map file for the extended statement. Has anyone
else noticed this problem before or am I the first to try extending
across maps? I looked at fixing it but it gets a bit more complicated
with parameter maps, etc. My use case is really just a raw select that
acts as the base for all queries that expect to return the particular
result map.
Thanks,
Chris
--------------------------------------------------------
Princeton Retirement Group, Inc - Important Terms
This E-mail is not intended for distribution to, or use by, any person or entity in any location where such distribution or use would be contrary to law or regulation, or which would subject Princeton Retirement Group, Inc. or any affiliate to any registration requirement within such location.
This E-mail may contain privileged or confidential information or may otherwise be protected by work product immunity or other legal rules. No confidentiality or privilege is waived or lost by any mistransmission. Access, copying or re-use of information by non-intended or non-authorized recipients is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail.
The transmission and content of this E-mail cannot be guaranteed to be secure or error-free. Therefore, we cannot represent that the information in this E-mail is complete, accurate, uncorrupted, timely or free of viruses, and Princeton Retirement Group, Inc. cannot accept any liability for E-mails that have been altered in the course of delivery. Princeton Retirement Group, Inc. reserves the right to monitor, review and retain all electronic communications, including E-mail, traveling through its networks and systems (subject to and in accordance with local laws). If any of your details are incorrect or if you no longer wish to receive mailings such as this by E-mail please contact the sender by reply E-mail.
--------------------------------------------------------