I haven't had a chance to test the 2.3.x release. Has the problem with
Oracle ref cursors been fixed then? It's not that we couldn't move
forward (we discovered that stored functions work just fine nearly a
year ago, and that's our standard approach); in fact we have 6 projects
using the same
What you're experiencing is really a limitation in iBATIS 2 dynamic
SQL. The legacy generator generated *a lot* of code and still was
pretty limited in function. The new generators generate better code
IMHO, and you really can create very flexible WHERE clauses. There are
still some inefficiencies
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.java (e.g attributeA,
Is there a way to include the table name in the column resultmap
definitions generated by ibator?
This would be very useful when having joins with column name collisions:
An example:
- TABLE "PRODUCT" having ID and NAME columns
- TABLE "CATEGORY" having ID and NAME columns
Ibator gene
I was wondering if the new build are going to be available on Maven central
repository EVER! Any news?
--
View this message in context:
http://www.nabble.com/New-iBATIS-build-on-Maven-central-repository.-tp18964458p18964458.html
Sent from the iBATIS - User - Java mailing list archive at Nabble.c
You can ask (a)ibator to generate an alias for the tables and column names -
I think that work for this situation. See the "alias" attribute on the
element:
http://svn.apache.org/repos/asf/ibatis/trunk/java/tools/ibator/core/htmldoc/configreference/table.html
Jeff Butler
On Wed, Aug 13, 2008 a
Sorry - just read your post a little closer and see that you know about
alias already. Why won't alias work?
select a.id as a_id, a.name as a_name, b.id as b_id, b.name as b_name
from product a join category b on
where a.id = b.id
Jeff Butle
Hi Jeff,
thanks for your quick reply!
Defining an alias is only half way in my opinion:
Using an alias helps to avoid a join column name collision but you still
cannot use "*" in your queries and have to type every column and column
alias in your queries ("select a.id as a_id, ...") as def
What database are you using? What you describe is some kind of auto
aliasing that I have not seen before. For example,
select product.*, category.*
from product join category on product.id = category.id
should return ID, NAME, ID, NAME
NOT
PRODUCT.ID, PRODUCT.NAME, CATEGORY.ID, CATEGORY.NAME
AFAIK, SYSTEM in XML is only "supposed" to be an URI, and does not necesarily
need to be some accessible HTTP URL - it may point to the document autor's
system and may not make sence in user's system. PUBLIC is what editors etc
should map to their DTD repository.
There's also some discussion whic
10 matches
Mail list logo