title: Zend 2 changing database design
body: <p>We are planning to develop a web app (front-end + back-end + business logic + model) for a client using the Zend 2 framework. </p>
  
  <p>One of our developers fears and claims (arguably) that the database tables design has to be done once and for all at the beginning of the project, that we should not tolerate any future fields or entities to be added to the design in the future. </p>
  
  <p>Coming from an Agile (non-web) world, I am not really confortable with this claim and if required we would simply leave Zend for another framework. Allowing the client to add new features in the future to the tables diagram is essential to our project.</p>
  
  <p>Do you have any clues, ideas, documentation (official), that could support the hypothesis that Zend 2 is fit for evolutive design? And possible something less abstract than this: <a href="http://martinfowler.com/articles/evodb.html" rel="nofollow">http://martinfowler.com/articles/evodb.html</a></p>
  
  <p>Thanks a lot in advance.</p>