Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>First you can browse through the Rails api doc. Most of the times this would answer your questions. But for some questions you get stuck as you noticed.<br> This is mostly a sign that it will become difficult to get the answer, since no documentation is present. So you have two options: do not use the method/feature you were looking information for, but use something else. Or get ready to spend a lot of time browsing through <a href="http://github.com/rails/rails" rel="nofollow noreferrer">the Rails sources on github</a>.</p> <p>Use something like this <a href="http://www.google.nl/search?&amp;q=site%3Agithub.com+rails+activerecord+retrieve_connection" rel="nofollow noreferrer">Google query</a> to get access to the particular github part. This will mostly send you to the correct file, but at some blob instead of the master, so find the same file in the master tree, so you know the thing you are looking for is available in your Rails (assuming that you are using the master/unmodified version) Next part is more difficult, you found the <code>retrieve_connection</code> method by now, but it uses another method <code>retrieve_connection_pool</code>, which is used in another file somewhere in the <i>active_record/connection_adapters(/abstract)</i> directory path. Which is using some other class, found in ..., and so on ...</p> <p>This situation is mostly the case if you are browsing through the sources. After a while you will likely get the hang of it and become more used finding things you need. But it will always be a lot of work to find the answer this way.</p> <p>So the choice is yours I guess.</p> <p><strong>PS</strong> Instead of using the Rails API you can try to type in some of your keywords <em>ActiveRecord::Base.connection tables indexes</em> in Google and hope someone wrote an article on these subjects and did the Rails source research for you.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload