Cataloging events, projects and tasks: Is SQL appropriate?
I have this idea for a database: it would hold everything I “need to remember”, and allow future coding projects to access the information. These future projects include a day-planner and historical analysis of what I’ve been up to.
What’s a better name for this many-to-many table?
Part of one of my applications has contracts and contract_types tables, wherein a type may have many contracts but a contract may only be of one type. Now a new wrinkle has been introduced: a contract may change type over time (although it can, thankfully, still only be of one type at any one time).
Is it reasonable to use POCO’s that inherit from DTO’s?
I’m designing a tiered .NET application, and I want to use the Code First approach. I’m new to this, so I’m struggling to envision how it ought to be designed. Would the following be a reasonable approach? What problems or limitations might I run into?
User management data – the need for a username and password
I would have this asked on StackOverflow if it had code, but it’s more on the idea/concept so I asked here.
When using Hibernate can we forget about Database Design?
We started (just me and my friend) working on a website. As a part design phase we have finished the drawing a Site Map, decided on the content in each of the web page and the navigation.
Application Logic Vs DB Triggers for database cleaning
When cleaning out old data from a set of database tables, is it safer to have the logic in the application or in a database trigger?
How do you organize highly customized software?
I’m working on a large software project which is highly customized for various customers arround the world. This means that we have maybe 80% code which is common between the various customers, but also a lot of code which has to change from one customer to the other. In the past we did our development in separate repositories (SVN) and when a new project started (we have few, but large customers) created another repository based on whatever past project has the best code basis for our needs. This has worked in the past, but we ran into several problems:
Which aspect of normal forms do entity-attribute-value tables violate, if any?
I’m not asking if EAV tables are good or bad. I’m wondering if they are considered “normalized”, and if not, why? If they aren’t normalized, which normal form are they violating and why?
Would this data requirement suit a Document -Oriented database?
I have a requirement to allow users to fill in journal/diary entries per day.
I want to provide a handful of known journal templates with x columns to fill in. An example might be a thought diary; a user has to record a thought in one column, describe the situation, rate how they felt etc.
The limit of Int32 for Identity Column
This is just a consideration for a site am creating and for other big sites out there.