StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19784802
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-11-05T08:44:07.807
FavoriteCount
0
LastActivityDate
2013-11-05T09:38:37.567
LastEditDate
2013-11-05T09:38:37.567
LastEditorUserId
1189124
OwnerUserId
1189124
ParentId
15132379
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
You could do this by implementing custom <code>ErrorHandler</code> and overriding some of <code>AppKernel</code> methods. For example: <pre><code>class AppKernel { protected $prodErrorHandler; public function init() { if ($this->debug) { ini_set('display_errors', 1); error_reporting(-1); DebugUniversalClassLoader::enable(); ErrorHandler::register(); if ('cli' !== php_sapi_name()) { ExceptionHandler::register(); } } else { ini_set('display_errors', 0); error_reporting(-1); $this->prodErrorHandler = new CustomErrorHandler(); set_error_handler(array($this->prodErrorHandler, 'handle')); } } public function boot() { $booted = $this->booted; parent::boot(); if (!$booted && $this->prodErrorHandler !== null && $this->container->has('logger')) { $this->prodErrorHandler->setLogger($this->container->get('logger')); } } // ... other methods } class CustomErrorHandler { protected $logger; protected $buffer = array(); public function setLogger($logger) { $this->logger = $logger; foreach ($this->buffer as $error) { $this->logger->warning($error); } $this->buffer = array(); } public function handle($level, $message, $file, $line, $context) { if (error_reporting() & $level) { $error = new \ErrorException(sprintf('%s: %s in %s line %d', isset($this->levels[$level]) ? $this->levels[$level] : $level, $message, $file, $line)); if ($this->logger !== null) { $this->logger->warning($error); } else { $this->buffer[] = $error; } return true; // this would skip logging to file etc. Return false to just log and pass error handling to other handlers } else { return false; } } } </code></pre> Something similar can be done with separate Bundle too, but it can "skip" some of errors occurred before bundle is registered. If you use <code>Monolog 1.6</code> or later, you can also use <a href="https://github.com/Seldaek/monolog/blob/1.6.0/src/Monolog/ErrorHandler.php" rel="nofollow"><code>Monolog\ErrorHandler</code></a> to register logger for errors, unhandled exceptions and fatal errors.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLog warnings and notices in Symfony 2
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMarius Balčytis
UserOwnerUserId
1. USMarius Balčytis
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COGood idea. Thank!
 singulars
 PostPostId
 PO
 UserUserId
 USZhukV

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.