I have a bunch of products with a bunch of different possible attributes for each product. E.g. Product A has a name, size, color, shape. Product B has a name, calories, sugar, etc. One way to solve t
OK my first question so here goes. Currently users are using a huge Access Application. They wanted a web application with some functionality based off of the Access data and with some modifications.
I am considering designing a relational DB schema for a DB that never actually deletes anything (sets a deleted flag or something).
Lucene stores index for each field separetly. So when we perform query \"fld1:a AND fld2:b\" we iterate over Termdocs for first term and second term. This can\'t be faster. In case of database two sep
I have a database schema to log operations users perform in my webapp: Log --- Id Log_Type_Id Performed_by_Person_Id
I\'m confusing about 0:M relationship. So, I want to ask about that. Assumes we have 2 tables : Contact which has attributes like : ContactID(PK),
I have two tables, let\'s call them TableA and TableB. One record in TableA is related to one or more in TableB. But there\'s also one special record within them in TableB for each record from TableA
I\'m trying to figure out the best way to deal with the following situation. Let\'s say we have an entity type with attributes A, B and C. Each of these attributes can have a known set of possible va
I need to store images in a DB2 Blob field. The average image size is about 200KB but in rare cases there will be images with 2-4MB. I don\'t want to reject these images so I guess I\'d define a BLOB(
We are overhauling our product by completely moving from Microsoft and .NET family to open source (well one of the reasons is cost cutting and exponential increase in data).