Railsã§ãƒ¢ãƒ‡ãƒ«ãƒ‡ãƒ¼ã‚¿ã®ã‚¯ãƒ©ã‚¹ã‚’サブクラスã«å¤‰æ›´ã™ã‚‹ - tsimoã®ãƒ¡ãƒ¢
Single Table Inheritanceã§è¦ªå関係ã«ã‚る二ã¤ã®ã‚¯ãƒ©ã‚¹Hoge, FugaãŒã‚ã‚‹ã¨ã™ã‚‹ã€‚ class Hoge < ActiveRecord::Base end class Fuga < Hoge end ã“ã®ã¨ãHogeクラスã®ã‚ªãƒ–ジェクトaãŒã‚ã£ãŸã¨ã—ã¦ãれをFugaクラスã«å¤‰æ›ã—ãŸã„ã¨ã™ã‚‹ã€‚ ãã‚‚ãã‚‚ãã†ã„ã†çŠ¶æ³ãŒã‚ªãƒ–ジェクト指å‘çš„ã«ã©ã†ãªã®ã‹ã¨ã„ã†ã®ã¯ç½®ã„ã¦ãŠã。 ã“ã®ã¨ã〠a = Hoge.find(1) b = a.becomes(Fuga) b.save! ã¨ã™ã‚Œã°ã„ã„ã®ã‹ã¨æ€ã£ã¦è©¦ã—ã¦ã¿ã‚‹ã‚‚ã€ãƒãƒ¼ãƒ‰ã—ãªãŠã—ãŸã‚ªãƒ–ジェクトã¯Hogeクラスã®ã¾ã¾ã ã£ãŸã€‚ オブジェクトをä¿å˜ã™ã‚‹ã¨ãã®ã‚¯ã‚¨ãƒªãƒ¼ã‚’見るã¨æ¬¡ã®ã‚ˆã†ã«ãªã£ã¦ã„ãŸã€‚ UPDATE `hoges` SET `type` = 'Fuga', `updated_at` = '2013-04-08 14:0
Rails STI and form_for
Rails STI and form_forWritten August 14, 2012. Tagged Ruby on Rails, STI. Rails' form_for conveniently uses "record identification" to figure out the correct URL based on the model: = form_for([:admin, @item]) do |f| = f.text_field :nameIt's also used to figure out the HTTP verb, the field name prefixes, HTML classes and HTML id. So this form would POST to admin_items_path for a new record, or PUT
Rails Single Table Inheritance - What is the best way to explicitly set type?
I am using single table inheritance in my rails application, and want to explicitly set the type of an instance. I have the following; class Event < ActiveRecord::Base class SpecialEvent < Event which is implemented through single table inheritance. SpecialEvent.new works as expected, but I want to be able to do things like Event.new(:type => 'SpecialEvent') So I can create different sub_types eas
Rails STI and the development environment - Blog - Tim Harding - g0
I'm using single table inheiritance (STI) to model the foods people eat and use in recipes in SF. STI is a way of representing a class and its subclasses in a single database table. The system defines a WeightPortion is a UserPortion is a Portion and there are a couple of other subclasses too. Rails handles this pretty well in the case that it has loaded all the subclasses into memory and worked o
ApplicationModel クラスã®ã‚¹ã‚¹ãƒ¡ (STI ã¨ã®å…±å˜) - ヽ( ・∀・)ノãã¾ãã¾ãƒ¼(2007-09-02)
Rails ã§é•å’Œæ„Ÿã‚’覚ãˆã‚‹ã®ã¯ã€ãƒ¢ãƒ‡ãƒ«ã«ã ã‘アプリケーション層ã«åŸºåº•ã‚¯ãƒ©ã‚¹ãŒç”¨æ„ã•ã‚Œã¦ã„ãªã„所。é•å’Œæ„Ÿã®æ£ä½“ã¯MVCã®å¯¾ç§°æ€§ã ã‘ã§ã¯ãªãã€å®Ÿéš›ã«ä¸ä¾¿ãªã®ã 。ã“ã“ã§è¨€ã†ã€Œã‚¢ãƒ—リケーション層ã®åŸºåº•ã‚¯ãƒ©ã‚¹ã€ã¨ã¯ã€ãƒ•ãƒ¬ãƒ¼ãƒ ワークレベルã«ç›´æŽ¥å®šç¾©ã™ã‚‹ã®ã¯æ°—ãŒã²ã‘ã‚‹ã‘ã©ã€ç¾åœ¨ã®ã‚¢ãƒ—リケーションã§è‡ªåˆ†ãŒå®šç¾©ã™ã‚‹ã‚¯ãƒ©ã‚¹å…¨ä½“ã«ã¯å½±éŸ¿ã‚’与ãˆãŸã„よã†ãªå®šç¾©ã‚’è¡Œã†ã‚¯ãƒ©ã‚¹ã®æ„。例ãˆã°ã€ã‚»ãƒƒã‚·ãƒ§ãƒ³æƒ…å ±ã§ã‚ã‚Œã°ã€ãƒ•ãƒ¬ãƒ¼ãƒ ワークレベルã§ãªãã€ApplicationControllerã«å®šç¾©ã™ã‚‹ã®ãŒè‡ªç„¶ã ã—ã€ç¾åœ¨ã® ActionPack ã§ã‚‚ãã†ã„ã†å®Ÿè£…ã«ãªã£ã¦ã„る。åŒã˜ã“ã¨ãŒãƒ“ュー(ヘルパ)ã«ãŠã„ã¦ã‚‚å¯èƒ½ã ãŒã€ãƒ¢ãƒ‡ãƒ«ã ã‘ã¯ãªãœã‹ ActiveRecord::Base を直接継承ã—ã¦ãŠã‚Šã€ã“ã‚ŒãŒä¸ä¾¿ãªå±€é¢ãŒå¤šã€…ã‚る。 ApplicationModel 具体的ã«ã¯ã€æ—¢å˜ã®NKSKプãƒã‚¸ã‚§ã‚¯ãƒˆã®ãƒ¢ãƒ‡ãƒ«(クラス群)を別ã®ãƒ—ãƒã‚¸
Definitive Guide to Single Table Inheritance (Page 1) - Models and Database - Rails Forum - Ruby on Rails Help and Discussion Forum
After trying to implement this in my project I am realizing just how scant and misleading the docs are on this topic. This thread is more of a request than a tutorial and I am hoping that some of you more experienced Rails folk will fill out the missing pieces of the puzzle.To make your jobs easier, I will cover what I do know...When to use STI: This structure is best used for models that have ide
Mixing Single Table Inheritance and RESTful routes
I am trying to implement a restful app, but I have found some problems with the design, when I have thought in implementig STI. I will try to explain. Only as a example, you may suppose this models Class Person < ActiveRecord::Base has_many :widgets end Class Customer < Person end Class Employee < Person end Class Widget < ActiveRecord::Base belongs_to :person end Then I would like to define these
Single Table Inheritance in Rails [Alex Reisner]
Because single table inheritance (STI) has been invaluable to me in some recent Rails projects, I thought I’d try to dispel a little of its negative reputation by writing about some reasons you might use it, when to avoid it, and some tips for working with it. If you gave up on Rails’s STI a while ago because it required too many workarounds, I’d recommend giving it another look, as some annoyance
1
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Baseclass becomes! subclass by ehtb · Pull Request #14971 · rails/rails
{{#tags}}- {{label}}
{{/tags}}