Grails default controller implementation does not properly validate domain objects before attempting to persist to database

When attempting to save a new domain object, the default implementation of the controller's save makes a new instance of the object and calls hibernate to save. If there are any errors (i.e. constraint validation fails), the page is rendered again w/ the list of failing constraints. However, if a user then proceeds to view a list of all saved objects via a call to the controller's list method, the invalid object is still persisted to the database and now the database is corrupted.