是否可以返回数据集而不是MyBatis中的任何映射模型类?

时间:2019-04-16 07:09:34

标签: java reflection mybatis

我有一种情况,我想进行myBatis应该支持的动态查询,如下所示:


    <select id=“someRecords” resultMap=“someRecordMap”>

        DROP TABLE IF EXISTS TEMP_TABLE;
        CREATE TEMPORARY TABLE TEMP_TABLE(some_stub UUID);

        INSERT INTO TEMP_TABLE (some_stub)
        select regexp_split_to_table(#{someIds},',')::uuid;

        SELECT wil.some_identifier_stub as identifier_stub
        ,wil.x
        ,wil.y
        ,wil.z
        ,wil.u
        ,wil.o
        ,msg.p
        FROM TABLE_A msg
        INNER JOIN TABLE_B wil ON msg.a_id = wil.b_id
        INNER JOIN TABLE_C est ON est.c_stub = wil.b_stub
        WHERE wil.unique_id = #{uniqueId} AND wil.b_type_id = #{b_TypeId}
        <if test="environment != null">
            <include refid="environmentCondition"></include>
        </if>
    </select>

    <sql id="environmentCondition">
        AND environment = #{environment}
    </sql>

但是我想返回DataSet,而不是someRecordMap,以便它与我现有的代码向后兼容

因此,我没有使用myBatis XMl方法,而是使用如下所示的反射和注释进行自定义方法:

部分:基于某些条件的动态查询,例如IGNORE_SOME_JOIN,IGNORE_SOME_STUB,IGNORE_SOME_EXT_FLAG


    @SqlQueries({@SqlQuery(name = "query1",
                query = "select a,b," +
                        "c,d,e,f,g,wil.h," +
                        " j,h,i " +
                        START_DELIMITER + " " + IGNORE_SOME_JOIN + " " +
                        " ,some_message" + END_DELIMITER +
                        " FROM  A_TABLE wil " +
                        START_DELIMITER + " " + IGNORE_SOME_JOIN + " " +
                        "LEFT OUTER JOIN B_TABLE wim on" +
                        " wil.unique_id = wim.unique_id" +
                        " and wim.created_date >= ?  and wim.created_date <= ?  " + END_DELIMITER +
                        " WHERE ( wil.created_date >= ? AND wil.created_date <= ? AND wil.primary_id = ? " +
                        START_DELIMITER + " " + IGNORE_SOME_STUB + " " +
                        " AND wil.unique_identifier_stub = ?::uuid " + END_DELIMITER +
                        START_DELIMITER + " " + IGNORE_SOME_EXT_FLAG +
                        " AND wil.some_ext_success_flag = ANY(?) " + END_DELIMITER + ")" +
                        "ORDER BY wil.created_date OFFSET ? LIMIT ? ")}
        )

动态查询的解析逻辑类似于


    abstract class ReportingQuery {
        private static final Logger LOG = LoggerFactory.getLogger(ReportingQuery.class);

        static final String START_DELIMITER = "#~";
        static final String END_DELIMITER = "#~";
        static final String REPLACEABLE_DELIMITER = "--";

        /**
         * Responsible to prepare final query after applying dynamic query criteria
         *
         * @param className     : ReportingQuery class reference
         * @param methodName    : Query method name
         * @param queryName     : Dynamic query
         * @param ignoreStrings : Criteria to be applied in dynamic query
         * @return : final static query after applying dynamic query criteria(ignoreStrings)
         */
        static Optional<String> getQuery(Class className, String methodName, String queryName, List<String> ignoreStrings) {
            StringBuilder builder = new StringBuilder();
            try {
                Method[] methods = className.getDeclaredMethods();
                Optional<String> queryString = Optional.empty();
                if (Arrays.stream(methods).anyMatch(x -> x.getName().equals(methodName))) {
                    QueryExample.SqlQuery[] sqlQueries = Arrays.stream(methods)
                            .filter(x -> x.getName().equals(methodName))
                            .findFirst().get().getAnnotation(ReportingQuery.SqlQueries.class).value();
                    if (Arrays.stream(sqlQueries).anyMatch(x -> x.name().equals(queryName))) {
                        queryString = Optional.of(Arrays.stream(sqlQueries).filter(x -> x.name()
                                .equals(queryName)).findFirst().get().query());
                    }
                }

                String[] token = new String[0];
                if (queryString.isPresent()) {
                    token = queryString.get().split(START_DELIMITER);
                }


               ...... SOME logic to make query based on some dynamic condition

            return Optional.of(builder.toString());
        }

        /**
         *
         */
        @Retention(RetentionPolicy.RUNTIME)
        @Target({ElementType.METHOD})
        @interface SqlQuery {
            String name();

            String query();
        }

        /**
         *
         */
        @Retention(RetentionPolicy.RUNTIME)
        @Target({ElementType.METHOD})
        @interface SqlQueries {
            SqlQuery[] value();
        }
    }

所以如果我有条件IGNORE_SOME_JOIN,那么我的逻辑最后查询将是


    select a,b,c,d,e,f,g,wil.h,j,h,i FROM  A_TABLE wil WHERE ( wil.created_date >= '2018-08-29T15:15:42.42'
            AND wil.created_date <= '2018-08-30T15:15:42.42' AND wil.acct_id = 2000017
             AND wil.unique_identifier_stub = 'a004f322-1003-40a7-a54b-f3b979744fd2'
             AND wil.some_ext_success_flag  = ANY('{"0","1"}')) ORDER BY wil.created_date OFFSET 0 LIMIT 500;

因此,在上面我得到了作为字符串的查询,我将在下面的代码中运行并获得结果集:


     PreparedStatement ps = con.prepareStatement(query)) {
                    prepareStatement(prepareStatementAndQueryList, ps, con);
                    try (ResultSet rs = ps.executeQuery()) {
                    DO SOMETHING WITH RESULT SET NOW
    }
    }

但是我想用MyBatis来做这件事,而不是我自己的自定义解决方案,该解决方案很少出错,并且由于我在这里使用了很多反射,因此可能没有效率。

1 个答案:

答案 0 :(得分:0)

是的,这是可能的,并且mybatis直接支持。这是来自documentation的示例:

@SelectProvider(type = UserSqlBuilder.class, method = "buildGetUsersByName")
List<User> getUsersByName(String name);

class UserSqlBuilder {
  public static String buildGetUsersByName(final String name) {
    return new SQL(){{
      SELECT("*");
      FROM("users");
      if (name != null) {
        WHERE("name like #{value} || '%'");
      }
      ORDER_BY("id");
    }}.toString();
  }
}

在上面的示例中,getUsersByName是一种映射器方法,并且映射器使用UserSqlBuilder来基于映射器参数动态生成SQL查询文本。这正是您所需要的,并且与ReportingQuery的工作非常相似。

您需要调整代码,以便您现有的查询生成器确认使用SelectProvider API,但这似乎很简单。