Posted by jay.lee.bio on May 8, 2012 at 4:33pm
I'm wondering if it's ok to add a new field even if it would've been ok to add an existing field? I ask because I'm getting the impression that I'm not supposed to add an existing field unless I'm absolutely sure about it. I'm thinking it'll be easier to fix having added a new field that should've been an existing field vs the other way around (I'm not even sure if it's possible to fix having added an existing field when it really should've been a new field). Am I correct or am I confusing myself?
Comments
I wouldn't worry about it
I wouldn't worry about it that much unless someone knows something I don't can chime in.
It's not that hard to fix either case. You just add a new field and dump the values into one or the other.
The only thing you should consider is look forward as far as possible to make sure you dont have to fix something by painting yourself into a corner.
Existing fields should be used to maintain normalized values, if you are putting the same exact thing into a bunch of different fields with no distinct reason why then you might be over doing it.
Performance
If it's a huge site with lots of data or a small site with the potential to grow, I would suggest using new fields. Each field has a database table associated with it. If you reuse fields, the table will grow which would potentially turn into a performance hit. By creating new fields, each field will have its own table in the database which would result in less of a performance hit.
On the other hand, if it's a site with manageable amount of data, reuse fields. It will make coding easier, if you're doing any back end stuff. It will also make life with views easier, since you won't have select a from multiple fields.
Hope that helps.
Thanks guys! :D
Thanks guys! :D
Jay Lee
https://jay.lee.bio