You could leave it to "create-tables" or even "drop-and-create-tables" during development if your model is frequently changing.
During production I would turn if off and either switch to maintaining the tables with a script, or run it once to generate the production schema. Normally a production schema would be maintained by a DBA.
But it depends on your application. If your application can be downloaded and installed by many different users, then it may make sense to leave DDL generation on to avoid the user having to create the database. A few failed exceptions at startup should not have a big impact.