Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As it turns out, fixing this whole thing was a two step process.</p> <p>Because our production and development environments require different IPs <code>app/etc/local.xml</code> is untracked and instead we track <code>app/etc/local-example.xml</code> so that all of our developers can quickly and easily copy it over to <code>app/etc/local.xml</code> and be up and running. This has become a bit of a company standard and we use it across all of our other projects. Thankfully, one of my coworkers discovered that <a href="https://stackoverflow.com/questions/11515237/magento-cache-not-get-clear#comment15235264_11516317">Magento loads all the xml files in <code>app/etc/</code>.</a> </p> <p>So, no, our development IP wasn't magically cached in some crazy obscure location, we were just inadvertently loading it. After renaming that file to <code>app/etc/local.xml.example</code> it stopped referencing our development IP. Yay!</p> <p>Now, this isn't directly related to the question, but because the solution introduced a new bug I want to mention it. Once we renamed the xml file and cleared all of the caches we started seeing a new error.</p> <p><code>PHP Fatal error: Call to a member function setQueryHook() on a non-object in app/code/core/Mage/Core/Model/Resource/Setup.php on line 347</code></p> <p>In our example file we were defining our database resource inside a single <code>&lt;default_setup /&gt;</code> node. For our production environment we actually have <a href="http://mysql-mmm.org/" rel="nofollow noreferrer">a triple-m setup</a> with separate IPs for read and write queries so for production instead of a single <code>&lt;default_setup /&gt;</code> node we had <code>&lt;default_read /&gt;</code> and <code>&lt;default_write /&gt;</code> nodes. I have never been able to find documentation on exactly what is allowed and required in resources, but the read / write split was setup per <a href="https://stackoverflow.com/a/8972193/488663">the instructions in another StackOverflow post on the topic</a> and, up until today, worked great.</p> <p>On a hunch, I renamed the <code>&lt;default_write /&gt;</code> node to <code>&lt;default_setup /&gt;</code> and everything magically began working again. I'm not yet sure if the reads and write are correctly splitting, but I'll update this answer once I confirm everything is working.</p>
    singulars
    1. This table or related slice is empty.
    1. POMagento database IP is cached
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USJake A. Smith
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMagento database IP is cached
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks, solved me some hours of searching.
      singulars
      1. PO
      1. USAlekc
    2. COHey, did you ever figure out what was wrong with your `<default_write>` node?
      singulars
      1. PO
      1. USJMTyler
    3. COSadly, no, I never had the chance to come back around to that and I have since moved on from that project.
      singulars
      1. PO
      1. USJake A. Smith
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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