![]() My first though is to make a 'Component' class, with Component, Header, Area, and Product as its subclasses. I've got my entities divided into three object types, Header, Area, and Product. I'm starting to think that the best way to prevent these issues is to normalize the object. However, the number of these objects is causing issues with loading the data, and we're having to split up the XML and load a different 'Components' xml to each entity. I'm working on a project which has a large number of 'Enitity' objects that need to be stored in the database.Ĭurrently these entities are defined in their own XML files, which are then parsed into the object before storing them into the database. Is creating a "normalized" entity structure a good way to prevent future data issues? Microsoft Windows XP 圆4.Ĭategory:Software companies of the United StatesĬategory:Software companies established in 1992Q: 5.0.524.0.Īdobe Photoshop CS3 Cracked-Setup-Software. All The Software And Games Free Download Full Version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |