<commit_before>[Week 7 Home](../)

# U3.W7: Modeling a Real-World Database (SOLO CHALLENGE)

## Learning Competencies
- Create a graphical representation of a simple database
- Adhere to established naming conventions for DB tables and columns
- Identify database relationships including one to many, many to many, and one to one


## Summary
In this challenge, you'll take what you know about Twitter's users and tweets to create a schema design that models a real-world database. 

**NOTE:** We do not expect or what you to use the API. We want you to look at twitter's interface, identify some fields they collect for all users, then identify the fields used for tweets, and make a schema that shows that information. 

Make sure to commit your changes after each release!

## Release 0: User Fields
Go to [Twitter](https://twitter.com/) and check out your user profile. Identify the fields Twitter stores for each user in your [my_solution.md](my_solution.md) file.

## Release 1: Tweet Fields
Now look at creating a new tweet. What fields are available? Put the fields you've identified in your [my_solution.md](my_solution.md) file.

## Release 2: Explain the Relationship
What is the relationship between `users` and `tweets`? Where are they connected, do you think? Explain your answer. 

## Release 3: Make the Schema
Now go to [SQL Designer](http://socrates.devbootcamp.com/sql) and create your tables and fields. Take a screen shot and put it in the [imgs](../imgs) directory and then display it in your solution file.

## Release 4: Create SQL Statements to access your tables and return:
- all the tweets for a certain user id
- the tweets for a certain user id that were made after last Wednesday (whatever last Wednesday was for you)
- all the tweets associated with a given user's twitter handle
- the twitter handle associated with a given tweet id 

Put your SQL Statements in the appropriate section in your [my_solution.md](my_solution.md) file.

## Release 5: [Reflect](../../references/reflection.md) 
...in the reflection section of your [my_solution.md](my_solution.md) file. 

<commit_msg>added challenge and solution template<commit_after>[Week 7 Home](../)

# U3.W7: Modeling a Real-World Database (SOLO CHALLENGE)

## Learning Competencies
- Create a graphical representation of a simple database
- Adhere to established naming conventions for DB tables and columns
- Identify database relationships including one to many, many to many, and one to one


## Summary
In this challenge, you'll take what you know about Twitter's users and tweets to create a schema design that models a real-world database. 

**NOTE:** We do not expect or want you to use the API. We want you to look at twitter's interface, identify some fields they collect for all users, then identify the fields used for tweets, and make a schema that shows that information. 

Make sure to commit your changes after each release!

## Release 0: User Fields
Go to [Twitter](https://twitter.com/) and check out your user profile. Identify the fields Twitter stores for each user in your [my_solution.md](my_solution.md) file.

## Release 1: Tweet Fields
Now look at creating a new tweet. What fields are available? Put the fields you've identified in your [my_solution.md](my_solution.md) file.

## Release 2: Explain the Relationship
What is the relationship between `users` and `tweets`? Where are they connected, do you think? Explain your answer. 

## Release 3: Make the Schema
Now go to [SQL Designer](http://socrates.devbootcamp.com/sql) and create your tables and fields. Take a screen shot and put it in the [imgs](../imgs) directory and then display it in your solution file.

## Release 4: Create SQL Statements to access your tables and return:
- all the tweets for a certain user id
- the tweets for a certain user id that were made after last Wednesday (whatever last Wednesday was for you)
- all the tweets associated with a given user's twitter handle
- the twitter handle associated with a given tweet id 

Put your SQL Statements in the appropriate section in your [my_solution.md](my_solution.md) file.

## Release 5: [Reflect](../../references/reflection.md) 
...in the reflection section of your [my_solution.md](my_solution.md) file. 


{'fraction_non_alphanumeric': 0.07102539981185324, 'fraction_numerical': 0.0042333019755409216, 'mean_word_length': 4.296388542963886, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5211804', 'n_tokens_mistral': 1171, 'n_tokens_neox': 1077, 'n_words': 618}