Question: If I have 2 items with 1-1 strong dependency then one is an attribute i.e. column in the other one's table.  

E.g. if we have a movie database and each movie must have a review score (*review score is a number that represents the average score from X number of viewers*) and each review score belongs to a movie then the review score should be a column in the table Movie.  

Now if the review score comes from X number of people that actually did the review then this should be part of the Movie database too as a column.  

But seems weird to me because the number of people is an attribute of the review score not of the movie right?  

Am I misunderstanding something in this database design approach/theory?

Answer: 
You can use the [General Sibling Selector](https://www.sitepoint.com/web-foundations/general-sibling-selector-css-selector/) `~` selector instead of the [Adjacent Sibling Selector](https://www.sitepoint.com/web-foundations/adjacent-sibling-selector-css-selector/) `+` selector, like this:

```
#hover:hover ~ #squash {
  display: block;
}

```

**[JSFiddle](https://jsfiddle.net/r0ccynkx/1/)**

You can read more about different CSS sibling selectors [here](https://www.sitepoint.com/contiguous-sibling-selector/).
Depends on what you put in between the 2 parts. If text encase squash inside the  

```
<p> text here
    <div id="squash"...>
    </div>
</p>

```

Then css changes to

```
#hover:hover + p #squash {

```