Last modified: 2012-10-16 16:41:27 UTC
Not a high priority now, but would be nice.... If I have $wgContentHandlerUseDB = false now, but later decide to enable it, it could be nice to convert pages like JS and CSS pages to the appropriate content models. This could be either a script and/or on saving / purging a page. In my database, my JS page retains NULL content format and model in the page and revision tables.
NULL means "the default". It is also used when $wgContentHandlerUseDB is true, to preserve space. We could have a third mode, $wgAlwaysStoreContentModelInDB or whatever, that would cause the model to always be made explicit in the database. This would make the wiki robust against changing a namespace's default content model. But it would also use a lot of space for very redundant data (in wikipedia's case, a dozen million repetitions of the string "wikitext"). If you want such an explicit mode, please change the description accordingly. Otherwise, I'll close at wontfix.
