# 100% polymorphism problem, hmm not so sure

**URL:** <https://www.ruby-forum.com/t/100-polymorphism-problem-hmm-not-so-sure/109550>\
**Category:** Rails\
**Created:** [July 16, 2007, 7:48pm UTC](https://www.ruby-forum.com/t/100-polymorphism-problem-hmm-not-so-sure/109550 "2007-07-16T19:48:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![michau](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@michau](https://www.ruby-forum.com/u/michau)\
**Post date:** [July 16, 2007, 7:48pm UTC](https://www.ruby-forum.com/t/100-polymorphism-problem-hmm-not-so-sure/109550/1 "2007-07-16T19:48:48Z")

</div>

I have a problem to break down and implement.

At first look it seems, as if it should be done in polymorphic way. I  
imagine it as having this “abstract” class model Thing and then many  
many many different concrete\_thing\_types. My doubt is though - I am  
not really able to tell now what and how many of those different  
concrete\_thing\_types there will be. There may be “hundreds” of them  
and during the application’s lifecycle, that set will probably expand.

Any suggestions then?

Cheers,

M
