| ## | |
| # Hello hello! | |
| # | |
| # This is meant to be a quick (and fun?) sense-check of your Ruby! | |
| # | |
| # Notes: | |
| # 0. How are you today? 👋 | |
| # 1. Feel free to download the CSV locally paste into irb or run this with `ruby requests.rb`! | |
| # 2. We're loosely available to field questions on recruiting+engineering@trychameleon.com | |
| # 3. Don't overanalyze your implementation/formatting/variable names/etc. do what comes naturally to you |
| unless Rails.env.production? | |
| connection = ActiveRecord::Base.connection | |
| connection.tables.each do |table| | |
| connection.execute("TRUNCATE #{table}") unless table == "schema_migrations" | |
| end | |
| sql = File.read('db/import.sql') | |
| statements = sql.split(/;$/) | |
| statements.pop |
After years of coding and debugging my code, I've had to search for a lot of bug fixes online. Because of this, I've come up up with multiple googling techniques. I'd like to share these techniques here, to help others save time while searching for code solutions online.
These are techniques that apply to any type of online search you want to do, not just coding. Later on I'll touch on the subject of how to deal with error messages, and code searches.
First, Create a folder inside of lib called seeds
Put your CSV file example.csv into the lib/seeds folder. In the example below, the file is called real_estate_transactions.csv
Make sure you've created a resource with the appropriate columns to match your seed data. The names don't have to match up.
