Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 63958

The development of the conceptual schema and/or the logical model and/or the physical settings of a database.

1
vote
Neither of your approaches is good. You have Tests that produce Results for some Measurement that is done with some Method. The Method may applies to multiple Test. (see sample Data below) So this i …
answered Apr 29 '15 by xuma202
0
votes
Though reads are more common on these votes than writes. From my understanding you always load the vote count together with the question when displaying it. Therefore I would recommend storing them to …
answered Jul 25 '15 by xuma202
1
vote
I'd go with the 2nd approach. Don't be afraid of Join(t)s. Here are some reasons Fast enough. Chances are extremly low that you'd rely on the additional speed you gain from a flat structure, if ther …
answered Apr 29 '15 by xuma202
1
vote
Initially I have thought to only have reference to "car_model" in "posts" table. Cause technically I could access the car make via the "car_model" table. But then decided that for search purposes i …
answered Apr 22 '15 by xuma202
0
votes
Without any knowledge of CouchDB. Storing every version though may only differs marginal from its predecessor is a waste of storage. I'd recommend storing changes only. You might want to take a look …
answered Apr 29 '15 by xuma202
2
votes
The tables student and major are good. However following improvements can/should be made. Merge the FKs in MajorStudent to a PK, getting rid of the id Save a StudentFK and MajorFK rather than a Maj …
answered Apr 29 '15 by xuma202
1
vote
Approach 1 is the cleanest with no redundancy. However I can understand your worries about scanning through a huge table just to count a post votes. So approach 2 which features some "caching" seams …
answered Apr 29 '15 by xuma202
1
vote
I'll try to explain why they merge all relationships into one table. Whether a users follows, likes or comments a photo all these activities are somewhat similar they involve a user and photo. Note t …
answered Apr 29 '15 by xuma202
0
votes
Yes this design is poor, just imagine to add another hour. This is a better aproach: Students(**StudentID**, LastName, ...[other Student Details]) Courses(**CouseID**, Description, ...[any other Co …
answered Apr 29 '15 by xuma202