Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Given your explanation of your domain, I've whipped up a small test-driven example of how you might solve your problem. If you see any domain inconsistencies, please feel free to clarify further (I'm using my <a href="http://github.com/nakajima/acts_as_fu" rel="noreferrer"><code>acts_as_fu gem</code></a> to whip up test models on the fly).</p> <pre><code>require 'acts_as_fu' # class Task &lt; ActiveRecord::Base build_model(:tasks) do integer :task_target_id has_many :task_targets has_many :customer_stores, :through =&gt; :task_targets, :source =&gt; :targetable, :source_type =&gt; 'CustomerStore' has_many :software_systems, :through =&gt; :task_targets, :source =&gt; :targetable, :source_type =&gt; 'SoftwareSystem' end # class TaskTarget &lt; ActiveRecord::Base build_model(:task_targets) do string :targetable_type integer :targetable_id integer :task_id belongs_to :targetable, :polymorphic =&gt; true belongs_to :task end # class CustomerStore &lt; ActiveRecord::Base build_model(:customer_stores) do has_many :task_targets, :as =&gt; :targetable has_many :tasks, :through =&gt; :task_targets end # class SoftwareSystem &lt; ActiveRecord::Base build_model(:software_systems) do has_many :task_targets, :as =&gt; :targetable has_many :tasks, :through =&gt; :task_targets end require 'test/unit' class PolymorphicDomainTest &lt; Test::Unit::TestCase # Test that customer stores can have multiple tasks def test_customer_store_gets_task task = Task.create! customer_store = CustomerStore.create! customer_store.task_targets.create! :task =&gt; task assert customer_store.tasks.include?(task) end def test_many_customer_stores_get_task task_a = Task.create! task_b = Task.create! customer_store = CustomerStore.create! :tasks =&gt; [task_a, task_b] assert customer_store.tasks.include?(task_a) assert customer_store.tasks.include?(task_b) end # Test that software systems can have multiple tasks def test_software_system_gets_task task = Task.create! software_system = SoftwareSystem.create! software_system.task_targets.create! :task =&gt; task assert software_system.tasks.include?(task) end def test_many_software_systems_get_task task_a = Task.create! task_b = Task.create! software_system = SoftwareSystem.create! :tasks =&gt; [task_a, task_b] assert software_system.tasks.include?(task_a) assert software_system.tasks.include?(task_b) end # Test that Tasks can have multiple customer stores def test_task_has_many_customer_stores task = Task.create! customer_store_a = CustomerStore.create! customer_store_b = CustomerStore.create! task.customer_stores = [customer_store_a, customer_store_b] task.save! task.reload assert task.customer_stores.include?(customer_store_a) assert task.customer_stores.include?(customer_store_b) end # Test that Tasks can have multiple software systems def test_task_has_many_software_systems task = Task.create! software_system_a = SoftwareSystem.create! software_system_b = SoftwareSystem.create! task.software_systems = [software_system_a, software_system_b] task.save! task.reload assert task.software_systems.include?(software_system_a) assert task.software_systems.include?(software_system_b) end end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POPolymorphic habtm relationships with Rails/ActiveRecord
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USnakajima
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis looks pretty good! My only concern is that I'm stuck defining each "targetable" in "Tasks". Is there a way to get around this? What about Task.targets/targetables?
      singulars
      1. PO
      1. USAlexander Trauzzi
    2. COI've been gnawing on this for most of today and I'm still not quite satisfied with what I have... It stems from: "has_many :customer_stores, :through => :task_targets, :source => :targetable, :source_type => 'CustomerStore' has_many :software_systems, :through => :task_targets, :source => :targetable, :source_type => 'SoftwareSystem'" Which to me defeats the purpose of polymorphic relationships all together. Is there any way to get it set up so I can get all targetables through Task.target AS WELL as being able to to Targetable.tasks?
      singulars
      1. PO
      1. USAlexander Trauzzi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload