> This is said because the datastore has cheap diskspace and there isn't
> good support for joins here.
Actually, that's not why folks say denormalize on app engine.
They say denormalize because the app engine infrastructure makes a lot
of normalization difficult. That difficulty is a consequen
Whoops, this posted twice. I posted once, and didn't see it for
hours, so I posted basically the same message.
On Sep 29, 2:55 pm, clay wrote:
> The death of normalization is premature. I wouldn't drink the
> denormalization coolaid yet.
>
> Sure joins are difficult in GAE, and disk space is c
This is said because the datastore has cheap diskspace and there isn't
good support for joins here.
However, we'll "relearn" why normalization is good.
Denormalization means that what would normally modify a single cell
will have to modify many rows. This isn't ideal in a relational
database, n
The death of normalization is premature. I wouldn't drink the
denormalization coolaid yet.
Sure joins are difficult in GAE, and disk space is cheap, however when
you change one atomic value in a denormalized database, you'll have to
change many rows, which itself can be slow, especially in GAE.
The datastore isn't a relational database, so articles about
relational databases for the most part don't apply.
On Sep 28, 7:54 am, jerry ramphisa wrote:
> Hi there,
>
> I hear normalizing the database is bad if you are using google
> datastore. On other other hand, most articles mention people
