# Many assets design question

**URL:** <https://www.ruby-forum.com/t/many-assets-design-question/111462>\
**Category:** Rails\
**Created:** [August 7, 2007, 4:45pm UTC](https://www.ruby-forum.com/t/many-assets-design-question/111462 "2007-08-07T16:45:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pabloz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/c37758/32.png) [@pabloz](https://www.ruby-forum.com/u/pabloz)\
**Post date:** [August 7, 2007, 4:45pm UTC](https://www.ruby-forum.com/t/many-assets-design-question/111462/1 "2007-08-07T16:45:14Z")

</div>

Hi!

In my recent app I will have stuff like projects, references. Project  
will have many assets like images and pdf’s. Reference will only have 1  
asset - one image.

Is it good idea to build polymorphic resource like ASSET and try to put  
every asset in there and have something like Attachable type = Project  
or Reference??

If so, are there any examples that might help me?

PS.

I found something like [http://sample.caboo.se/](http://sample.caboo.se/) - In this app  
attachment\_fu with resource\_fu is being used to build this kind of  
relationship.