Possible Duplicate:
Is there ever a time where using a database 1:1 relationship makes sense?
For the sake of simplicity, I'll ask the question straight out: should one-to-one relationships in database design be avoided or this acceptable?
I know all of the attributes of this "item" can be all hosted in ONE table, but I feel when converting my database design into business objects via an ORM, it clutters the entity with unnecessary properties.
Via the UI, hopefully this will paint a better picture, I have a main form with all of the necessary attributes. I will have a button that will allow the user to click on it and it will bring up a new form to attach extra attributes. No more than 1 entry can be affiliated with the main form (entity), i.e. it is a 0..1 end relationship.
Any advice will be appreciated.