so far i havent been able to find a way to document my database with rails. is this a flaw? a feature? a hidden feature? or they just dont care about documenting the database? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Fernando wrote:> so far i havent been able to find a way to document my database with > rails. > is this a flaw? a feature? a hidden feature? or they just dont care > about documenting the database?You could just put comments in your migrations. They are ruby code. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On 7 Nov 2008, at 01:30, Norm wrote:> > Fernando wrote: >> so far i havent been able to find a way to document my database with >> rails. >> is this a flaw? a feature? a hidden feature? or they just dont care >> about documenting the database? > You could just put comments in your migrations. They are ruby code. >That''s not that great, for example a table''s structure can be the accretion of multiple migrations. The rails way is probably just to keep that sort of stuff in the appropriate model (and since the rails way is not to use things like triggers and what not, the model encapsulates pretty much all the intelligence in the app). Fred> >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Along the same lines as Fred suggests, it should be on the model. We''ve been using the annotate_models to do it for us. http://agilewebdevelopment.com/plugins/annotate_models -H On Nov 7, 5:17 am, Frederick Cheung <frederick.che...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 7 Nov 2008, at 01:30, Norm wrote: > > > > > Fernando wrote: > >> so far i havent been able to find a way to document my database with > >> rails. > >> is this a flaw? a feature? a hidden feature? or they just dont care > >> about documenting the database? > > You could just put comments in your migrations. They are ruby code. > > That''s not that great, for example a table''s structure can be the > accretion of multiple migrations. > The rails way is probably just to keep that sort of stuff in the > appropriate model (and since the rails way is not to use things like > triggers and what not, the model encapsulates pretty much all the > intelligence in the app). > > Fred > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---