Using OGNL in includes for better routing.

It's currently not possible to do dynamic routing using OGNL in includes. It's pretty cumbersome to write out a separate select with a choose/when structure in order to assert an include routing, when a naming scheme will do just fine.

Would it be possible to allow OGNL in the refid attribute of include or create a separate attribute for OGNL based routing?

[harawata]

If I understand you correctly, it would be possible to write the choose/when in a sql element rather than in every select element.

@harawata I currently use a choose/when sql fragment as a router list, however this is incredibly annoying to manage and maintain.

Using OGNL would allow you to automatically find the proper fragment name based on a naming scheme.

For example I have a file that has a 2 dedicated fragments that basically look like this

<sql id="includes">
<choose>
<when test="selectId = com.mymybatis.custom.mymapper.statement1">
<include refid="com.mymybatis.custom.mymapper.statement1extension"/>
</when>

<when test="selectId = com.mymybatis.custom.mymapper.statement2">
<include refid="com.mymybatis.custom.mymapper.statement2extension"/>
</when>

<when test="selectId = com.mymybatis.custom.mymapper.statement3">
<include refid="com.mymybatis.custom.mymapper.statement3extension"/>
</when>

...
</choose>
</sql>

Then this is called from a different fragment looking somewhat like this

<sql id="driver">
with
include as (
<include refid=`includes`/>
)
full as
(
<!-- this is my second giant block router -->
<include refid=`views`/>
)
select
<include refid="generate_fields"/>
from full
where
<include refid="generate_where"/>
</sql>

The select statements simply include driver.

[harawata]

Hi @pignatenko
Just a heads up. Check out #331 to see if it could be a solution to your problem.