encukou/test-1 — Issue #73: Investigate collapsing versions in pokemon_moves
Author: encukou
Created: 2011-11-03 19:55:36+00:00
State: open
Labels: involved

**Reported by [En-Cu-Kou](http://github.com/encukou) on 2011/09/22 15:04:28 +0000 · Migrated from [Redmine issue 672](http://bugs.veekun.com/issues/672)**

---

A whole lot of rows in pokemon*moves could be saved if the versions are collapsed at the DB level, using first*version*group*id and last*version*group*id instead of version*group\_id.

A similar approach is already used in move changelogs.

Adding Colosseum, XD, etc. makes this more urgent.

Redmine metadata:
Updated on: 2011/09/23 00:39:07 +0000
Start date: 2011/09/22

---

**Comment by [Eevee](http://bugs.veekun.com/users/1) from 2011/09/23 00:39:07 +0000**

i am reeeeally wary of doing this

a few places are denormalized where we’d end up spending a ton of app effort making normalized data useful: move changes, for example.

doing this to pokemon\_moves would make the data harder to query **and** harder to present. all it would save us is space. except it wouldn’t, because the old version is still in git.