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?
Data Quality in Relational Database Regression Tests
I have been working on an open source Museum Collections Management web application that is to be used to keep track of a museum’s accessioned, donated, loaned or otherwise acquired artefacts.
Externalising SQL Queries in Java
What are the advantages and disadvantages of externalising SQL queries in Java (or similar general-purpose object-oriented programming language. Externalizing means storing all SQL in a separate non-java file or files. Several good examples are here.
How can I implement a database TableView like thing in C++?
How can I implement a TableView like thing in C++?
Should I create an Enum mapping to my database table
I have a database table containing a list of systems relevant to the tool I am building, mostly in-house applications, or third-party systems we receive data from. This table is added to infrequently, approx every 2 months.
Predicting advantages of database denormalization
I was always taught to strive for the highest Normal Form of database normalization, and we were taught Bernstein’s Synthesis algorithm to achieve 3NF. This is all very well and it feels nice to normalize your database, knowing that fields can be modified while retaining consistency.
On merging database records, constraint violation in the intermediate table of M2M
If you are merging two or more database records from table X, that have a many-to-many relationship with table Y, how should you solve the problem of records in intermediate table Z that would violate one or more constraints as a result of the merge? Do you simply discard them or break off the transaction?
Type of AI to tackle this problem?
I posted this on stackoverflow but want to get your recommendations as well as a user on overflow recommended I post it here.
Designing persistence schema for BigTable on AppEngine
I have tried to design the datastore schema for a very small application. That schema would have been very simple, if not trivial, using a relational database with foreign keys, many-to-many relations, joins, etc.
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.