Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POHow to increase Heroku log drain verbosity to include all Rails app details?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USHristo Deshev
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI have added Progstr, however I'm still not seeing additional verbosity in my log output (ie, things that I think that I should see from log/*). Is there something that I'm missing in terms of the config/environments/<env>.rb? I wonder, for example, even though I have set `heroku config:add LOG_LEVEL=DEBUG`, and I have "config.consider_all_requests_local = true" set for seeing exceptions more clearly, I still cannot pull out database queries and seemingly all of the additionally verbose info that I should be seeing in log/*. Obviously logging in via the shell in Cedar isn't sufficient.
      singulars
      1. PO
      1. USylluminate
    2. CO@ylluminate, the problem is that the ActiveRecord logger will log SQL statements with a DEBUG level. Rails goes out of its way to stop logging debug events in production (which is a good thing really). You can still make it log the SQL debug statements by tweaking the Rails logger and its log device. Or you can add the `progstr-ruby` gem and set up the `Progstr::RailsLogger` class as described here: http://docs.progstr.com/#local_setup . Note that `Progstr::RailsLogger` delivers events straight to our servers and does not route them to the syslog drain. Ex: http://i.imgur.com/DxF2B.png
      singulars
      1. PO
      1. USHristo Deshev
    3. COI have installed progstr, however I very much want to see this additional info spewed forth for all staging events (ie, not production). To set this up, I simply copied the production.rb over to staging.rb and tweaked a few settings, but I suspect there is a way to coerce staging to act like development in this logging regard?
      singulars
      1. PO
      1. USylluminate
 

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