I have two entities: Dealers and Makes. Dealers have multiple makes.I am able to insert the records as a one-to-many relationship between these two entities.
I am designing database for web base(ASP.NET) Phone-book - Contact manager software. Each contact may has different phone types .. (Home , Work , Mobile ,etc ...)
I have a book structure with Chapter, Subchapter, Section, Subsection, Article and unknown number of subarticles, sub-subarticles, sub-sub-subarticles etc.
I want to create a database to store the competition tables for (European) football. What I initially wanted to have was a single table for all competitions with a competition_id column.
here is a little challenge for you fellow overflower. I am working with a database of products that we sell into our Web based quotation application. Each product has the following attributes:
If I am keeping a collection of people in a SQL database, and each person has a separate collection of objects of the same data type, what is the best way to store the objects and keep them linked to
I am designing a database and I wish it could support more than one version in another words, if I have an object - info, it can have one value on one version and another value on another version.
after a few discussions with a collegue we still not have the same meaning about this topic. In my opinion it makes more sense to create a properly designed Database with all including relations.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical andcannot be reasonably answered in its current form. For help clari
Does it matter how many databases I use in my web system? I am planning to have: User information and related tables
加载中,请稍侯......