Write Java data applications like SQL-TINYSQLDSL

Preface
Words of enterprise applications, generally inseparable from the database. To do a database, there can be n scenarios, such as: directly using the JDBC layer in its own package, with some framework, such as: ibatis,hiberate,spring JDBC template and so on (this is too many, so not enumerated), These programs also show their own characteristics in their respective fields, solve a considerable part of the technical problems, and achieved a fairly good application effect.
But no matter what kind of solution, its advantages and disadvantages are often linked together, the reason is because the SQL and Java programming is fragmented, if the package is not in place, the Java people are too difficult to use, if the package too much, when doing some complex SQL is very cumbersome. Hibernate, for example, uses the encapsulation hql approach to solve this problem. Ibatis is good for SQL support, but there is a sense of fragmentation, but also in the resolution of the introduction of dynamic SQL to solve the problems that need to be handled according to some runtime conditions, to a certain extent, increase the complexity of the use.
So the question is, is there a better way to solve the problem in the database application development process? The root cause is how to solve the problem of the fragmentation between SQL and Java code in database development, if we can solve this problem, theoretically there will be a good solution.
We know that SQL is actually a domain of data for the DSL language, if we can write SQL directly in Java, and then execute the results can be directly returned to the Java object, this problem does not have a good solution?
TINYSQLDSL Solutions
In fact, there are some ready-made solutions, but some are not open source, and some support is not very in place, so leisurely decided to try to write, write a half-day time to see the effect, seerestful style of support practiceArticle, internal discussion, feel good, so formally decided to take the time to write a tinysqldsl, of course, the actual writing, there are a lot of problems, so that the final style and the above article there are some inconsistencies, of course, this is normal, easy to understand, Otherwise it would be too divine.
Our common SQL statements have Select, Insert, Update, Delete, so our scenario also implements how these statements are written.
First look at the TINYSQLDSL version of DAO is how to write.
First step: Define Pojo

1. <strong>public class Custom {
3. Private String ID;
5. private String name;
7. private int age;
9. Public String getId () {
10. return ID;
11. }
13. public void SetId (String id) {
14. This.id = ID;
15. }
17. Public String GetName () {
18. return name;
19. }
21. public void SetName (String name) {
22. THIS.name = name;
23. }
25. public int getage () {
26. return age;
27. }
29. public void Setage (int.) {
30. This.age = age;
31. }
33. }
34. </strong>

Copy Code

Step two: Define the table structure definition file

1. public class Customtable extends Table {
2. public static final Customtable CUSTOM = new customtable ();
3. Public final Column ID = new column (This, "id");
4. Public final column NAME = new column (This, "NAME");
5. Public final column Age = new column (This, ' age ');
7. Private Customtable () {
8. Super ("Custom");
9. }
10. }

Copy Code

Step three: Writing the DAO class

2. public class Customdao {
4. Private Dslsession dslsession;
8. Public Dslsession getdslsession () {
10. return dslsession;
12. }
16. public void Setdslsession (Dslsession dslsession) {
18. This.dslsession = dslsession;
20. }
24. public void Insertcustom (custom custom) {
26. Dslsession.execute (
28. Insertinto (CUSTOM). VALUES (
30. CUSTOM. Id.value (Custom.getid ()),
32. CUSTOM. Name.value (Custom.getname ()),
34. CUSTOM. Age.value (Custom.getage ())
36. )
38. );
40. }
44. public void Updatecustom (custom custom) {
46. Dslsession.execute (
48. Update (CUSTOM). Set (
50. CUSTOM. Name.value (Custom.getname ()),
52. CUSTOM. Age.value (Custom.getage ())). WHERE (
54. CUSTOM. Id.eq (Custom.getid ())
56. )
58. );
60. }
64. public void Deletecustom (String id) {
66. Dslsession.execute (
68. Delete (CUSTOM). WHERE (
70. CUSTOM. Id.eq (ID)
72. )
74. );
76. }
80. Public Custom Getcustombyid (String ID) {
82. Return Dslsession.fetchoneresult (
84. Selectfrom (CUSTOM). WHERE (
86. CUSTOM. Id.eq (ID)
88. )
90. , Custom.class);
92. }
96. Public list<custom> Querycustom (custom custom) {
98. Return Dslsession.fetchlist (
100. Selectfrom (CUSTOM). WHERE (
102. and (
104. CUSTOM. Id.eq (Custom.getid ()),
106. CUSTOM. Name.equal (Custom.getname ()),
108. CUSTOM. Age.equal (Custom.getage ())
110. )
112. )
114. , Custom.class);
116. }
118. }

Copy Code

Look at the above example, will it feel a little strange, how can you write this? Oh, don't worry about the actual implementation mechanism, we first taste this DSL-style database writing method, um, specifically, like writing SQL in the same way to write SQL.

Write Java data applications like SQL-TINYSQLDSL