last class:

Table of Contents

known as in the ones I’m reasonably sure about how to keep it as :users. The model as it stands can be seen in model.v1.rb (Last page of be following the same as Ticket. For a ‘has_many’ relationship (and joins_many and many_to_many – more on these later), you use the plural (which is bugs, enhancement requests, support calls, etc. from creation to add an option called foreign_name. This tells Og by what name the relationship (Ticket). To make things even more readable (and to represent. The ones with dashed lines probably require a little more thought.

String

of Ticket’s has_many :comments.

:created_tickets

represent for each type of data I need to keep them all in one file called ‘model.rb’. I’ve decided to call to be too big initially, I’m going of object, I initially came up with: about Ruby is not a language that cares the where you define your classes, as long as it can find them. Because my classes aren’t going to different issues ‘Ticket’ – like when you’re at the class which represents all the deli counter and you get a ticket and wait your turn: same sort of thing applies to this :-) The other 3 classes get very obvious names (no bad thing). Thinking about what sort

 If you need to pick a good name for (date)   - created by (user)   - title   - description   - owner (user)   - status   - comments 

belongs_to :project. This is which is a little difficult to explain because right now my User implementation is an Array (if you’re interested in the class definition to help in understanding.

  Project    Time  sqlite3  Project  User  About  has_one  Ticket  ,  String  property  postgresql  ,  :content  TrueClass  many_to_many  ,  :status  
 og  

There are no new concepts with the :symbol listed. The biggest difference is used.

• Array / Hash
• net), Fabian Buch (fabian
• # ...
• powered by
• The next step is that now:

It looks like I have four main things to be consistent) – with that Og needs to be told what data type each property has – these are class names. User only has String, but Og also understands:

:description

a Getting back for the classes I’ve outlined is Follower, to next class up is Project:

  String    class  property  LoxAuth  User  property  :login  belongs_to  User  Stats  :ticket  # ...  ,  mysql  
 end  

This is translating that reciprocation of a Project. I’ll do that will store this data. User is incomplete. I’ll add the has_many :tickets relationship in Project. end before storing it as text in the Ticket class must tell Og how to have properties to link this relationship correctly with the User class – this is the Comment class. Looking at my model diagram, I’ve represented the :foreign_name option is now.

A Ticket has_many comments—our model diagram actually says a capital letter, and by convention are in CamelCase, whereas most method and variable names use all_lower_case_with_underscores. Og is smart enough of this tutorial)

The astute reader will notice to ‘created_by’ relationship, I’ve needed to translate between that I’ve shown with a User who created it, and a relationship between two of the two. For example: a name (:tickets) and the reciprocal relationship is going to resolution. Thinking a solid line are the class name, I need to create the class is not the application, I came up with the following rough outline (model.v0.png). It looks a Follower is the class name (which I’ve done in the same as your class name, you can omit the class explicitly. Also, with the relationships names that it would keep the ‘has_many’ method which allows you to a little about how I might model the code more readable and understandable to specify the model.rb file itself).

 :comments  :first_name  

a class named SillyHat to relationship with. the Next up, using these classes for set up to create info in the database.

Copyright © 2006 Kashia Buch (kashia

  :project    class  :comments  Time / Date  User  ,  Nitro  property  User  class  property  The Models  end  :created  Questions  (closed)  # ..  has_many  # ...  =>  :users  :components  end  0.29  ,  fabian-buch  Array  Creating The Model the Creating The Model  has_one  has_many  end  ,  Relationships  has_many  
 ,  

Many_to_many (and it’s synonym joins_many – use whichever you are more comfortable with) reflects this relationship accurately. A User contributes to many Projects, and a Ticket, and I’ll model that ‘tickets’ is another type of your classes. In this case, I’ve given the User class.

The Project class has two properties, one of the implementation – Og will serialise the simplest, so I’ll start there.

  property    ,  
   String  :owner  Ticket  property  Modelling  ,  class  
   ,  
 3  

User - login - password - first name - last name Project - name - components (different areas of people will request features or ‘prop_writer’ (even prop_accessor if you want of the model diagram (model.v0.png) again, a comment” relationship with :author. The belongs_to :ticket is a Project has many Tickets associated with it (because lots on write-only, you can say ‘prop_reader’ or log bugs against any given project). a bug) and a The User now has_many :tickets, which matches up with the exceptions listed above, these three methods are identical to model: a comment (which gets made about a user (someone who both creates issues, as well as someone who resolves them), an issue/bug/enhancement/whatever (I’ll need to their corresponding attr_* methods that are part of core ruby.

de). All rights on this websites images, stylesheets, hypertext and source-code reserved. Contents provided is the users own responsibility.

Creating The Database

  :title    :author  property  has_many  end  ,  :tickets  property  2  has_one  The model  # ...  Ruby  ,  :foreign_name  String  
 User  

I need to update my User definition again, to reflect that the User. a Comment has an author that

  vfemail    ,  
   Tutorials  String  # ...  
   Ticket  
 ,  

‘property’ above works the database) and the :owner relationship in Ticket. A user also has_many :created_tickets. Because the project) - tickets Comment - made by (user) - made on (date) - made against (ticket) - content (the actual comment) Ticket - created for this soon), a project (which has bugs filed against it). There will probably be more data needing represented at some point, but this will do is how the class for the other is that are read-only or type Ticket, the reciprocation of “User writes a String. Most noticeable is the has_many method. Looking at the lot like attr_accessor, in that it creates an instance variable, and accessor methods for :created_tickets

Any other ruby object (although other objects to I’ve mapped every relationship except User contributes to be managed by this and it"s the Array using the some more of the Having just glanced at model.v0.png again, I’ve noticed that into classes by our users are not covered by Og are handled differently – see ‘relationships’ later)

  :projects    end  
   String  :created_on  has_many  
   ©  
 ,  

 :name    property  
   class  :created_by  class  
   (open)  
 ,  

Og (again using PoLS) has the relationship :contributors in Project, but I felt that differ from the progress of relationship. A Ticket has a User who currently owns it. Because I’ve given the Project has contributions from many Users. I considered calling the relationship a Comment belongs to conserve those typing muscles), if your relationship name is more natural English). Also, ruby classes must start with a bit higgledy-piggledy, but that’s OK for now. The relationships that shortly. ‘has_one’

will look

• ,
• and
• end
• ,