localization/globalization through sqlite

I don't see anything against using SQLite, except for

- a potential hit on performance

- the possible requirement for implementing the equivalent of a resource fallback strategy as described in

Creating and retrieving resources in Windows Store apps

ResourceManager.GetString Method (String, CultureInfo)

ResourceContext class

---

So, I would still stick with the classical resx. mechanism for (e.g.) screen labels but managing lots of 'complex and live' culture-dependent text would benefit from using a database