+1 This is an excellent example of one of my bigger frustration with the docs. If you don't happen to know what class something was actually implemented in, it is definitely a challenge to track it down. I think I do better with google and with the rak gem (grep for ruby) than with navigating the docs.
On Mon, May 3, 2010 at 7:32 PM, John Firebaugh <[email protected]>wrote: > Here's a documentation shortcoming I just came across: I was trying to find > the method that returns all tables in the database. I correctly guessed it > was Database#tables, but couldn't find it in the Database rdoc. Since the > method is only defined by individual adapter-specific subclasses, it doesn't > show up there. > > I suggest adding documentation in the base class for common adapter-defined > methods. Rdoc's :method: directive is good for this: > http://ruby-doc.org/ruby-1.9/classes/RDoc/Parser/Ruby.html > > -- > You received this message because you are subscribed to the Google Groups > "sequel-talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<sequel-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/sequel-talk?hl=en. > -- http://codeconnoisseur.org -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
