search

fasterthanlime / cs322

CS-323 project
2 stars 1 forks source link

Height #9

Closed nddrylliog closed 12 years ago

nddrylliog commented 12 years ago

Let's just store that in meters instead of having two columns.

@greut can you change the sql and update the tables in our DB to reflect this change?

nddrylliog commented 12 years ago

(Errata: I wrote 'weight' at first, whereas it's clearly 'height')

greut commented 12 years ago

I did that first but then revert that idea. We will have to convert that back and forth (loosing precision each time) with no win. I don't see what it brings.

nddrylliog commented 12 years ago

It's just that conceptually it seems really dirty to store a single (real-life) attributes in two different (database) attributes.

greut commented 12 years ago

As stupid as firstname and lastname, you'll lose precision by joining them. Somehow an extreme example I know.

We will have to convert them during the import one way and again the other way when displaying the results. I'd go for the lazy path here.

nddrylliog commented 12 years ago

I would think displaying them in meters would have been fine.. but if we really do need to display them in feet and inches, then okay.

greut commented 12 years ago

I'll go with storing everything in inches, 1 foot being 12 inches, the conversion is very easy (in both ways). “ils sont fous ces Anglais, ils sont fous!”