GQL - Google App Engine | Google Groups

GQL - Google App Engine | Google Groups:

> Denormalize X3? That strikes me as very bad. If a customer's name is
> corrected later, you would need to search down and change other
> entities, or lose the connection.

It's only bad if you can't write correct code.

You can maintain a core of relational entities that form your editable
database, and a published database that all the public read pages load
from. Yes, data redundancy. Denormalisation.

You can't scale without it.

The simple truth is that normalisation only makes sense when the
read:write ratio is close to 1:1. The web ain't nothing like that. Not
by a very long shot."