One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
| Here are two turnkey options in a SQL query to get the data schema (table names, columns, data types, etc.) from a PostgreSQL database—one **bash script** that uses `psql \copy` to write CSVs locally, and one **Python script** that does the same (and zips the results). Both include: **tables/columns/PKs/FKs/indexes, views, materialized views, sequences, and triggers**. | |
| Here’s where and how to set your own **file path** depending on which version you’re using: | |
| --- | |
| ## 🧩 If you’re using the **Python script** | |
| When you run: |
| Checkpoint 8: Deploy to Heroku. I got the correct result but I could not tell from the course guide. So I ended up asking office hours. What they told me is that the correct result will show an error. This is expected. The error is "The page you were looking for doesn't exist." It will say this on the web page of your app. The reason is that there is nothing in your app yet. | |
| Checkpoint 14: Intro to Classes. The first section on RSpec Class Errors is really helpful to understand RSpec. Would be great to somehow include these pointers in the RSpec section that comes earlier. | |
| General comments: | |
| - Give me a way to easily share my progress on social networks. Complete a checkpoint, be able to tweet it and post it on FB. | |
| - Include a section on tips for reading the RSpec error messages. Here is an example provided by my awesome mentor John: | |
| - Let's take apart the error message: exercise.rb:21: syntax error, unexpected '\n', expecting '=' (SyntaxError) | |
| The first part (exercise.rb:21) tells us it's on line 21 of t |