Search code examples
androiddatabasesqlitenormalization

Android Database Normalization

Since phones are not nearly as fast as computers, I can see having multiple joins in queries slow down the application.

With redundant data (or non-normalize) it seems like you will have a lot of duplicate data but faster queries.

So, in android/sqlite, is it better to normalize your database and therefore require more joins in queries or to simply have redundant data but use less joins?

Any suggestions would be great! Thanks!

Solution

  • I would go for normalizing the database, Processing power has improved significantly and running queries with joins would be easier than dealing with nightmare of de-normalized schema