Shulou(Shulou.com)06/02 Report--

This article will share with you about situations where iBATIS is not suitable for use. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

IBATIS is not suitable for use when you can always have full control

If you can guarantee complete control over application design and database design, you must be a very lucky person. This is rare in a business environment or in any industry where the core job is not software development. However, if you work for a software company and are developing a product that you have full design control over and sell by you, you may be in this situation.

When you have full control, there is a good reason to use a complete object / relational mapping scheme, such as Hibernate. You can take full advantage of the design advantages provided by object / relational mapping tools and increase productivity. There may be no interference from the enterprise database group at all, and there is no need to integrate with legacy systems. In addition, the database may be deployed with the application, which makes it within the scope of the application database (see Chapter 1). A good example of an application that uses Hibernate is Atlassian's JIRA. They provide a problem tracking software as a release product that they have complete control over.

However, the future development of applications needs to be considered. If the database is likely to be beyond the control of the application developer, you must carefully consider how using object / relational mapping will affect your persistence strategy.

IBATIS is not suitable for use 2 when your application needs fully dynamic SQL

If the core function of your application is to generate SQL dynamically, then iBATIS is the wrong choice. IBATIS supports very powerful dynamic SQL features, which in turn support advanced query capabilities and even some dynamic update capabilities. However, if every statement in your system is generated dynamically, then you *

One of the powerful features of iBATIS is that it allows you the complete freedom to write and manipulate SQL by hand. When most of the SQL in the application is generated dynamically from some SQL generation class, this advantage is quickly lost.

IBATIS is not suitable for use 3 when you are not using a relational database

For databases other than relational databases, JDBC drivers are also available. For flat files, Microsoft Excel spreadsheets, XML, and other types of data storage platforms, there are corresponding JDBC drivers. Although some people have been successful in using these drivers in iBATIS, we do not recommend using these drivers for most users.

IBATIS doesn't make any assumptions about your environment. But it does expect you to use a real relational database, that is, a relational database that supports semantics such as transactions, relatively typical SQL, and stored procedures. Even some very well-known databases may not support some important features of relational databases. For example, earlier versions of MySQL do not support transactions, so iBATIS does not handle MySQL very well. Fortunately, the current MySQL already supports transactions and there is also a very specification-compliant JDBC driver.

If you are not using a real relational database, we recommend that you use the original JDBC, or even the lower-level file I API.

IBATIS is not suitable for use 4 when iBATIS doesn't work

As the community puts forward more and more requirements, iBATIS continues to implement many very good features. However, iBATIS has its own development direction and design goals, so it may sometimes conflict with the needs of some applications. People can do a lot of amazing things with the help of software, but sometimes because the requirements are too complex, the software may not work at all, and so can iBATIS. Although we can also add features to iBATIS to support these complex requirements, doing so may greatly increase complexity and may even change the scope of the iBATIS framework. Therefore, we will not modify the framework. To solve the above problems, we will provide an extensible interface so that you can extend iBATIS to meet almost any need. In fact, sometimes iBATIS just doesn't work. At this point, * is looking for a better solution, rather than using iBATIS (or any other framework) in an inappropriate place.

Thank you for reading! This is the end of this article on "what are the situations in which iBATIS is not suitable for use?". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.