Following the myBatis guidelines #{} is used in your sql statements. If you take a look any of MyBatis Reference in the Section Mapper XML Files it says explicity: Notice the parameter notation: #{id} Otherwise ${} is for 1- Configuration properties. For example: <properties resource=”org/mybatis/example/config.properties”> <property name=”username” value=”dev_user”/> <property name=”password” value=”F2Fa3!33TYyg”/> </properties> Then the properties … Read more
You want to get a Map<Integer,String> where the Integer is the id and the String is the name. If there were 200 categories in your table, you would want 200 entries in your map, rather than a list of 200 maps. MyBatis can’t quite do that out of the box, but you can use its … Read more
Using Java 8 you could do it in one line: String addressID = addresses .stream() .map(a -> String.valueOf(a.addressId)) .collect(Collectors.joining(“,”));
I believe the answer is the same as is given in this question. You can use myBatis Dynamic SQL in your annotations by doing the following: @Select({“<script>”, “SELECT *”, “FROM blog”, “WHERE id IN”, “<foreach item=’item’ index=’index’ collection=’list'”, “open='(‘ separator=”,” close=”)”>”, “#{item}”, “</foreach>”, “</script>”}) List<Blog> selectBlogs(@Param(“list”) int[] ids); The <script> element enables dynamic SQL parsing … Read more
MyBatis is a fork from iBATIS, and according to Wikipedia most of iBATIS’ developers moved over to MyBatis too. The iBATIS project is currently marked as Inactive, therefore you should go with MyBatis for new projects and only use iBATIS if you’re maintaining an existing project which already uses iBATIS. http://en.wikipedia.org/wiki/MyBatis MyBatis is a fork … Read more
Let me take a crack at this. First of, I’ve written some on this subject in Using an ORM or plain SQL?. Specifically to address your points: Learning Curve/Ease of Use Ibatis is about SQL. If you know SQL the learning curve for ibatis is trivial. Ibatis does some things on top of SQL such … Read more
iBATIS and Hibernate are quite different beasts. The way I tend to look at it is this: Hibernate works better if your view is more object-centric. If however you view is more database-centric then iBATIS is a much stronger choice. If you’re in complete control of your schema and you don’t have an extremely high … Read more