I'm writing a small Ruby library:
class FizzBuzzEndpoint
def call(env)| /** | |
| * Select2 | |
| * | |
| * Renders Select2 - jQuery based replacement for select boxes | |
| * | |
| * Simply pass a 'config' object on your schema, with any options to pass into Select2. | |
| * See http://ivaynberg.github.com/select2/#documentation | |
| */ | |
| Backbone.Form.editors.Select2 = Backbone.Form.editors.Base.extend({ |
| MongoMapper::Railtie.class_eval do | |
| config.action_dispatch.rescue_responses.merge!( | |
| 'MongoMapper::DocumentNotFound' => :not_found | |
| ) | |
| end |
In reply to http://www.zopyx.de/blog/goodbye-mongodb
I'm answering the questions as if I'm answering the blogger, no you. :)
First order of business. http://facility9.com/2010/09/five-reasons-to-use-nosql/
MongoDB was deisgned for massive scale data storage and the architecture does it very well. A design decision is not a flaw if you do not like how it behaves in
| $ ruby -v | |
| ruby 1.9.2p136 (2010-12-25) | |
| $ ruby symbol_literals.rb | |
| valid as first char: | |
| @$_ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz | |
| valid as middle char: | |
| _ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 | |
| valid as end char: | |
| !_=?ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 |