Explore >> Select a destination
|
You are here 
|
fractaledmind.github.io | ||
| | | | |
smsohan.com
|
|
| | | | | I am working on ScrumPad chat refactoring now. In rails 2, the named_scope feature works really great for ActiveRecord models. Lets start with the code first- The Source Code: class ChatUser < ActiveRecord::Base belongs_to :chat belongs_to :user belongs_to :chat_status, :foreign_key => "status_id" named_scope :closed, lambda {|chat_id| {:conditions => ["status_id = #{ChatStatus::CLOSED} AND chat_id = ? ", chat_id]}} do def invite() each { |chat_user| chat_user.update_attribute(:status_id, ChatStatus::INVITED) } end end named_scope :active_chats, lambda {|user_id| {:conditions => [" | |
| | | | |
blog.codeminer42.com
|
|
| | | | | As we all know, it is quite easy to create database tables with Ruby On Rails. However, some cases require personalizations to reproduce real world situations and the relationships between them. Here, we have two models: User and Meeting, with a 1..N relation where one Meeting has two User (yes, a two-person meeting.) The problem | |
| | | | |
www.zombiezen.com
|
|
| | | | | Interacting with SQLite inside Visual Studio Code | |
| | | | |
jakeyesbeck.com
|
|
| | | Using AR Models in Rails migrations works but can have hidden problems. Learn why to avoid them and what to do instead | ||
