Databases
StackOverflow2013
Postsdbo
PORails dosen't log database queries
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails dosen't log database queries
    text
    copied!<p>I set in development.rb the following line:</p> <pre><code>config.log_level = :debug </code></pre> <p>The server starts normally, but it still doesn't log teh query, I expect to see the SELECT CREATE etc in the log, but nothing appears. I installed exceptional some time ago, it is possible that it bothers the regular log ? If yes, how to solve the problem ?</p> <p>EDIT 1 for the requirement of the answer:</p> <pre><code>ls -la log/ : totale 26416 drwx------ 2 marco marco 4096 18 giu 13.14 . drwx------ 15 marco marco 4096 5 lug 10.48 .. -rw-r--r-- 1 marco marco 27027849 18 lug 12.07 development.log -rw-r--r-- 1 marco marco 1578 18 giu 13.14 exceptional.log -rw-r--r-- 1 marco marco 2676 18 giu 13.14 production.log -rw-r--r-- 1 marco marco 0 18 giu 13.14 test.log cat ./Gemfile : source 'http://rubygems.org' gem 'rails', '3.0.3' gem 'exceptional' #Logging system in production group :development, :test do gem 'railroady' end # Bundle edge Rails instead: # gem 'rails', :git =&gt; 'git://github.com/rails/rails.git' gem 'sqlite3-ruby', :require =&gt; 'sqlite3' gem 'paperclip', '~&gt; 2.3' gem 'aws-s3' gem 'rails3-jquery-autocomplete' # Use unicorn as the web server # gem 'unicorn' # Deploy with Capistrano # gem 'capistrano' # To use debugger (ruby-debug for Ruby 1.8.7+, ruby-debug19 for Ruby 1.9.2+) # gem 'ruby-debug' # gem 'ruby-debug19' # Bundle the extra gems: # gem 'bj' # gem 'nokogiri' # gem 'sqlite3-ruby', :require =&gt; 'sqlite3' # gem 'aws-s3', :require =&gt; 'aws/s3' # Bundle gems for the local environment. Make sure to # put test-only gems in this group so their generators # and rake tasks are available in development mode: # group :development, :test do # gem 'webrat' # end </code></pre>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

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