It is a keyword in some contexts and not in (most) others. Is this not similar to SQLite's (parser's) willingness to permit some keywords as identifiers? Are those keywords specially mentioned in the docs? (No opinion or recommendation here, just consideration.) I do opine that the issue is not whether the tokenizer treats it as a keyword so much as whether it is good practice to avoid using the word as an identifier. That is why (I suppose) people look at keyword lists. "Good practice" encompasses avoiding the creation of confusing SQL, so that consideration may justify calling STORED and VIRTUAL keywords.