Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When using spring’s JdbcTemplate, I am using the row mapper to map results coming back.
The benefit with this is that there are less places where I have to change my code if I change my mysql schema etc.
Are there any other tips on how to minimize changes in code when adding/removing columns in mysql?
If you are retrieving columns by name (
SELECT col1, col2, col3) you will be immune to adding and rearranging of columns. Never useSELECT *.However if you are removing columns, you have no choice. In fact, how was this suppose to work? Previously you fetched e.g.
pricecolumn and used it in your business layer. Now the column does not exist – how to handle this?But adding columns is safe, unless new columns are non-nullable. In this case you will have a problem when adding new records, since
VALUESstatement won’t include new columns. Optional columns are fine.