The document provides tools and techniques for profiling and debugging Linux systems and Ruby applications. It discusses the lsof tool for listing open files, strace for tracing system calls…
use DBIx::Class::Storage::Statistics module's hook. package Your::DBIC::Profiler; use strict; use warnings; use base 'DBIx::Class::Storage::Statistics'; use Time::HiRes qw( tv_interval gettimeofday ); sub new { my ($class, $params) = @_; bless $params, $class; } sub query_start { my $self = shift; my $sql = shift; my $params = @_; my $bind = $params ? join(', ', @{$params})
NAME DBIx::Class::QueryLog - Log queries for later analysis. VERSION version 1.005001 SYNOPSIS DBIx::Class::QueryLog 'logs' each transaction and query executed so you can analyze what happened in the 'session'. It must be installed as the debugobj in DBIx::Class: use DBIx::Class::QueryLog::NotifyOnMax; use DBIx::Class::QueryLog::Analyzer; my $schema = ... # Get your schema! my $ql = DBIx::Class::Q
If you want a somewhat pretty picture of your DBIC schema (with relationships drawn, of course), install GraphViz, SQL::Translator, and DBICx::Deploy from the CPAN, and then run: $ dbicdeploy -Ilib MyApp::Schema ~/graphs GraphViz ~/graphs will then contain a .sql file that is actually a png of your schema. Rename it and see your schema in your favorite png viewing application. Oh yeah, the post ne
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く