When should we use weak entities when modelling a database?
This is basically a question about what are weak entities? When should we use them? How should they be modeled?
Storing revisions of a document
This is a follow up question to my original question. I’m thinking of going with generating diffs and storing those diffs in the database ‘History’ table.
Alternatives to sql like databases [closed]
Want to improve this post? Provide detailed answers to this question, including citations and an explanation of why your answer is correct. Answers without enough detail may be edited or deleted. As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, […]
Design Parts DB
I’m developing a tool that handles (electrical) parts. The parts can be created, viewed, modified, deleted, grouped and so on…
(Dis)advantages of datetime vs. long in globally used applications [closed]
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]
Should a database table(s) structure match its intended data structure(s) in the logic?
This question branches out of this question, What are the differences between algorithms using data structures and algorithms using databases?.
How should I represent an enumerated type in a relational database?
I am working on developing a relational database that tracks transactions that occur on a device I’m working on for my company. There are different types of transactions that could occur on the device, so we have a “trans_type” field in one of our main record tables. My group has decided to make the type of this field an integer and treating it as an enumerated type. My intuition tells me that it would be a better idea to make this field a string so that our database data would be more readable and usable. My co-workers seem to be worried that this would cause more trouble than it is worth. That string comparisons are too costly and the possibility of typos is too great of a barrier.
How to improve database schema with different n:m and 1:n associations between users/tasks/comments/attachments
I’m trying to build a database for an upcoming Ruby on Rails webproject.
Better way of storing key-value pairs in the database?
I have a C#/SQL Server program that sometimes needs to store data. The data could be a response from a web service, a result of a database query, or any number of other things. There’s no way of knowing before the data is stored how many fields it might have or what the data structure might be. We have this kind of painful table we’re using for this… four columns and lots of rows. An example of the data might be easier than an explanation.
Does this situation call for well specified associations, single table inheritance, or polymorphic association?
I’m building a web-app where users can keep track of who owes whom money.