id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,mlocked 13261,Better solution for schema or protocol mismatch,Peter Bennett,Peter Bennett,"There are compile options -DIGNORE_SCHEMA_VER_MISMATCH -DIGNORE_PROTO_VER_MISMATCH that nullify the database check and upgrade process and the protocol version check process. These seem to be dangerous options, particularly since they have to be compiled into the system to use them. There may be cases where you want to ignore schema or protocol mismatch. The attached patch allows the use of override parameters -O !IgnoreSchemaVerMismatch=1 -O !IgnoreProtoVerMismatch=1 at run time. This way you do not have to build the system with those dangerous options, you can ignore the errors for a single run. Also the IgnoreSchemaVerMismatch only works for mythfrontend. Using it on mythbackend may be risky. These options can also be stored in the settings table so that you could use a git-master version of mythfrontend with an older mythbackend as long as schema and protocol differences do not affect you. Often the master frontend has more advanced features that you may want to use, but you are not ready to upgrade the backend to master. The android packaging script uses those compile time options. Once this patch is committed we could modify the android packaging script to use the run-time options instead of the compile options. If we get to the stage where we offer the frontend on the google play store, we will need a frontend that supports more than one backend version, because the play store will always install the latest version. ",Patch - Feature,closed,minor,30.0,MythTV - General,Master Head,medium,Won't Fix,,,0