I made the classic mistake of assuming all imperial units; not much need for decimals in that case - so I had used INT types a lot of places where I was trackin

I made the classic mistake of assuming all imperial units; not much need for decimals in that case - so I had used INT types a lot of places where I was tracking weight. What a beginner mistake. Last night, recognizing that no one using the metric system could enter their weight in float form - I switched it to Floats thinking it wouldn't be an issue but due to the way GAE NDB datatstore works; it ended up rewriting the switched values to all None. I had pulled the trigger too soon. It was a clusterfudge. Ruined my night. But, that said -- atleast now the entire site is decimal/float friendly, as it should've been from the start. Fortunately, I'm the main person that had their data destroyed by the db change. You live and you learn.