Hi, I''ve got a table that stores urls, this is a simplified version Table urls: id, href Now, I want to crawls those hrefs and grab their title and METAtags, since every page could (and will) have a very distinct set of meta tags, I think the optimal way to store those goes like this: Table urls_meta: url_id, meta_name, meta_value Where every URL can have 0,1 or many corresponding records in the urls_meta table, right? Now, I want to throw a RoR frontend on top of this and I''m wondering which is the AR method to deal with this pattern. *I know* the simplest way would likely be to build a "Metatag" model that belongs_to the "Url" model. But I''m really interested, for the sake of learning, in knowing how to use AR in this case without that extra step, that is, keeping the metatag as an attribute of url, but an attribute that lives on a different table. I hope my explanation has not been too muddy and thanks in advance for your help. -- Manuel a veces :) a veces :( pero siempre trabajando duro para Simplelógica: apariencia, experiencia y comunicación en la web. http://simplelogica.net # (+34) 985 22 12 65 ¡Ah! y escribiendo en Logicola: http://simplelogica.net/logicola/ _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails