Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Templating has it's limits. However your problem can be solved very elegantly with Aspect. ( <a href="http://www.eclipse.org/aspectj/" rel="nofollow">http://www.eclipse.org/aspectj/</a> ) Just create a new annotation for every type of "template-case" you need and use an around advice.</p> <p><em>Ps: don't use printStackTrace() to syserr/sysout. There are so many production grade, lightweight logging frameworks.... pleeeaseee... don't abuse poor little System.out/err :)</em></p> <p>EDIT:</p> <p>Some example for a logging / benchmarking advice. <em>(note: I'm using spring AOP for aspects, and lombok for easy access to the logging framework. The <code>getCurrentUser()</code> code is not really relevant here, it's just for getting the current user from Spring Security)</em></p> <pre><code>package com.XXXXXXXX.aspects; import lombok.extern.slf4j.Slf4j; import org.aspectj.lang.ProceedingJoinPoint; import org.aspectj.lang.annotation.Around; import org.aspectj.lang.annotation.Aspect; import org.aspectj.lang.annotation.Pointcut; import org.springframework.security.core.context.SecurityContextHolder; import org.springframework.security.core.userdetails.UserDetails; import org.springframework.stereotype.Component; @Component @Aspect @Slf4j public class LoggerAspect { private final static String DOMAIN = "XXXXXXXX"; private static String getCurrentUser() { String username = "Unknown"; try { Object principal = SecurityContextHolder.getContext(). getAuthentication(). getPrincipal(); if (principal instanceof UserDetails) { username = ((UserDetails) principal).getUsername(); } else { username = principal.toString(); } } catch (Exception e) { } return username; } @Pointcut("within(com.XXXXXXXX.services..*)") public void inServiceLayer() { } @Pointcut("execution(* getMatcherInfo(..)) || execution(* resetCounter(..))") public void notToAdvise() { } @Around("com.XXXXXXXX.aspects.LoggerAspect.inServiceLayer() &amp;&amp; !com.XXXXXXXX.aspects.LoggerAspect.notToAdvise()") public Object doLogging(ProceedingJoinPoint pjp) throws Throwable { long start = System.nanoTime(); StringBuilder sb = new StringBuilder(DOMAIN); sb.append('/'). append(getCurrentUser()). append(" accessing "). append(pjp.getSignature(). getDeclaringTypeName()). append('.'). append(pjp.getSignature(). getName()); log.trace("START: " + sb.toString()); Object retVal = pjp.proceed(pjp.getArgs()); long duration = System.nanoTime() - start; log.trace("STOP: " + duration / 1000000 + " msec. " + sb.toString()); return retVal; } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POCustomize Try/Catch code template based on exception
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGergely Szilagyi
    1. USGergely Szilagyi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCustomize Try/Catch code template based on exception
      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. VTAcceptedByOriginator
    1. COGetting rid of that stupid print stack trace is exactly why I want to customize the template. ^_^ I've been in operations for more than a decade and I'm appalled at how often developers dump a stack trace when they should be handling the exception. I can understand it if it's something totally unexpected but you know, when you're accessing a file for example. There are some expected failure cases which are easily handled. ^_^
      singulars
      1. PO
      1. USTheSporkboy
    2. COWhat is Aspect? Aspect4j? I'm looking it up but what I see I'm not sure is what you're talking about.
      singulars
      1. PO
      1. USTheSporkboy
    3. CO@user1497207: added an aspect link to the answer
      singulars
      1. PO
      1. USGergely Szilagyi
 

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