This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
Run the following if you haven't already:
gem sources -a http://gems.github.com
Install the gem(s):
sudo gem install thoughtbot-pacecar
commit 49aca2009a077a9051ab189327482e1a27b67a22
tree 1019c33ca6f2b6648cd679fee8796ef37735cbeb
parent e909de91e898edfdc288013592fa296ff5993602
tree 1019c33ca6f2b6648cd679fee8796ef37735cbeb
parent e909de91e898edfdc288013592fa296ff5993602
... |
... |
|
... |
... |
|
... |
... |
|
... |
... |
|





Comments
Sadly SQL Server allows null on boolean’s. Insane? YES!
Yeah, so does mysql … but I don’t want to reward bad behavior by putting those methods out there. I think it’s best practice to put a not null constraint on rails boolean/tinyint columns, and default them to false.
Agreed, I’ve been in the habit of always forcing a :default and in the case of SQL Server doing an update all after adding said boolean to a table since it will leave all the existing records at NULL after the mig if I do not. Good work on the plugin too. I’m about to fork it and see if I can start to add some granular class declarations that generates batches of named_scopes vs the en-masse that is happening now. Cheers!