When upgrading, DB is noneditionable. Are there consequences of setting object to editionable?

When I upgraded a database to from 11g to 19c, the database is NONEDITIONABLE and so are all of the objects - for instance all the views.   When I run a simple CREATE or UPDATE View xzy statement it thinks I'm trying to change the VIEW to EDITIONABLE because I'm not specifying in the statement NONEDITIONABLE.   Does it make any difference if the view is set to EDITIONABLE if the SCHEMA is noneditionable?   Can I change the default behavior so that by default a CREATE OR REPLACE VIEW statement does not try to change it from NONEDITONABLE to EDITIONABLE?