/ruby-oo-relationships-practice-art-gallery-exercise

Primary LanguageRuby

Art Gallery Lab

In this project, we will be practicing object relationships in Ruby, with a particular emphasis on the has_many through relationship (aka: many-to-many). Please read the whole README before writing any code!

Introduction

You got yourself a fancy new job and you've been put in charge of making a program to keep track of paintings, and the galleries that are selling them.

Each painting has a price, and a title. Each artist has a name and an amount of years of experience, and each gallery has a name and a city.

The initial files and basic attributes have already been built, but you'll need to figure out the relationships and build the rest of the app out yourself!

Deliverables

Model the Domain

An artist can, of course, have many paintings. Paintings can only be in one gallery at a time, and only have one artist. Galleries can have many paintings.

  • What are your models?
  • What does your schema look like?
  • What are the relationships between your models?

Class Attributes and Methods

ARTIST

  • Artist#paintings

    • Returns an array all the paintings by an artist

  • Artist#galleries

    • Returns an array of all the galleries that an artist has paintings in

  • Artist#cities

    • Return an array of all cities that an artist has paintings in

  • Artist.total_experience

    • Returns an integer that is the total years of experience of all artists

  • Artist.most_prolific

    • Returns an instance of the artist with the highest amount of paintings per year of experience.

PAINTING

GALLERY

  • Gallery#paintings

    • Returns an array of all paintings in a gallery

  • Gallery#artists

    • Returns an array of all artists that have a painting in a gallery

  • Gallery#artist_names

    • Returns an array of the names of all artists that have a painting in a gallery

  • Gallery#most_expensive_painting

    • Returns an instance of the most expensive painting in a gallery