A lot of projects have a to be determined database model during early development. This could mean that a lot of SQL will have to be rewritten frequently. What is the recommended strategy to deal with this? Especially when you want to develop your application RAD-like and with the ultimate requirements not being set in stone at all? Mostly toy projects.
An ideal scenario would be that I can just not write any SQL at all at the start of the project, and only when the data model is more solidified, actually set up the database for the project and write SQL for it. During the initial development phase I just want to be able to alter my entity classes, without having to change my SQL over and over again.
(For the project I'm asking this, I'm working with Spring 4 and a MySQL database)