Understanding Markdown notation Notes for yourself
HTML,CSS,JavaScript,php Vue,Laravel I'm not good at the back end, so I was studying on my own, mainly around the front end.
--Bad point --Anyway, there is a lot of description ――It tends to be redundant --The type is too strict and the hurdle is high for beginners --Not modern --Maybe it's easy to get a waterfall ――The cost of learning is bad --Inevitably takes time
--Bad point --The description of Controller that may return to your own page may be unclear as to what process on which page (personal) --Because annotations are convenient, you may not notice basic errors (for beginners) ――It tends to be redundant ――It's hard to understand the version of STS tool ...
** Implementation items ** Login function for each administrator and user (Spring Security cannot be used) Cart function paging New registration, update, addition, search, compound condition search, logical deletion to DB
** Implementation items **
eclipse
Spring tool suite3 Spring Boot Spring Jdbc Spring Web Bean Validation
Thymeleaf MysqlWorkBench AWS S3
Every time I get stuck, there are many articles from quite a while ago. It's not that it doesn't work, but I'm worried about the modern writing style and technology.
I made an Entity according to the DB, but I was told that the Entity should not be displayed directly in the View, so I made a Model for display (the code content is exactly the same as the Entity except for the constructor) and used it as an argument of the constructor. Refilling was done by specifying Entity. I thought it would be okay to use the Clone method here, but he said he didn't need to clone it. The biggest problem was whether to create a Model for Form by updating DB records. After all the training, I heard that it depends on the product. Basically, it was said that it is okay to use one model instead of separating the models, but if there is a possibility that the contents of the DB will change in the future, or in the case of large-scale development, separate the models and use them properly. It was said that it was good.
I'm used to it, so I don't think it's going to get stuck. I couldn't move forward because I was stuck. It was packed with things to understand, such as the number of values and the type of data. It was even more confusing because DB join was involved in that situation. Especially for Timestamp and Date, I remember that the exchange with DB data became troublesome if I wasn't careful.
During development, I felt that anything related to validation or the value could change should be passed by Model. On the contrary, in most cases, I kept it in the session, and when I got used to it, I was wondering if it would be okay to delete all with invalidate (). There is also a method of passing it with hidden input, but I avoided using it because I think it will be an anti-pattern.
The most clogged was the transfer of data to and from the DB. First, the Mysql error message wasn't kind. And when the number of data increased, it became difficult to grasp what was passed and what was currently contained. One way was to make it easier to understand with the constants of Constants, but I personally avoided using it because it was difficult to understand.
Variable 1.compareTo (Variable 2)
"Negative value" if the method caller value (variable 1) is less than the argument value (variable 2) "Positive value" if the method caller value (variable 1) is greater than the argument value (variable 2) "0" if the value of the method caller (variable 1) is the same as the argument value (variable 2) Quoted from Samurai Academy
I found it convenient because it was easy to use for checking duplicate dates.
Recommended Posts