- Read every row in the table
- No reading of index. Reading from indexes is also expensive.
NOTE!!!!!!!!! Ended up in trouble going down this path. Followed Rails 3 in Action method instead
generate
rails plugin new importable --dummy-path=spec/dummy --full --mountable && cd importable
in .gitignore change references to test/dummy to spec/dummy (rails bug¿)
spec/dummy/db/*.sqlite3
spec/dummy/log/*.log
| #!/usr/bin/env ruby | |
| require 'socket' | |
| require 'timeout' | |
| unless ARGV.length == 2 | |
| abort "Usage: ruby #{__FILE__} HOST PORT" | |
| end | |
| def port_open?(ip, port, seconds=1) | |
| # => checks if a port is open or not on a remote host | |
| Timeout::timeout(seconds) do |
I use Namecheap.com as a registrar, and they resale SSL Certs from a number of other companies, including Comodo.
These are the steps I went through to set up an SSL cert.
Hierarchical data metrics that allows fast read operations on tree like structures.
Based on Left and Right fields that are set during tree traversal. When entered into node value is set to it's Left, when exiting node value is set to it's Right.
Unless you are using Safari on OSX, most browsers will have some kind of free plugin that you can use to export the browser's history. So that's probably the easiest way. The harder way, which seems to be what Safari wants is a bit more hacky but it will also work for other browsers. Turns out that most of them, including Safari, have their history saved in some kind of sqlite database file somewhere in your home directory.
The OSX Finder cheats a little bit and doesn't show us all the files that actually exist on our drive. It tries to protect us from ourselves by hiding some system and application-specific files. You can work around this by either using the terminal (my preferred method) or by using the Cmd+Shft+G in Finder.
Once you locate the file containing the browser's history, copy it to make a backup just in case we screw up.
