Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Monday morning ... classical time for not resisting a couple of comments :-)</p> <p>@timaschew</p> <ul> <li>"<em>need the propertyChangeListener, because it shows me the old and new value of the property.</em>" - (nitpicking - but always have this strong urge to separate requirement and solution :), I think it's the other way round: on a change notification you need access to both the old and new value, a propertyChangeEvent/Listener is a notification type which supports it, there might be others</li> <li>PropertyChangeSupport is not supposed to be used on part of the the <em>observing code</em>, it's supposed to be used on the <em>obervable</em>'s side (just as @Hovercraft did in his example): it's sole responsibility is manage and notify the listeners registered to the observable</li> <li>occasionally, accessibleContext provides a hook for hacks - nevertheless, it's a hack to hook into it (except you really need to support accessibility, which might well be the case :-) As with all hacks, that's a brittle solution which most probably will cause pain sometime in the future. Much more stable to follow the link about how Action and AbstractButton interact</li> </ul> <p>@Hovercraft</p> <ul> <li>enhancing the <em>model</em> with a richer change notification is the way-to-go (as in: my absolute favourite :-)</li> <li>just a small detail: if you have a slave let him do <em>all</em> the work - PropertyChangeSupport has methods which take the old/new value, no need to feed to create an event on the observable. It will be thrown away anyway when old and new are equal</li> <li>for newValue in the notification event, don't use the parameter but instead use getValue again (super might have rejected the change) </li> </ul> <p>@trashgod</p> <p>haha - you already guessed that I don't like solution: it breaks encapsulation in that it relies on an implementation detail, so don't except when in complete control of the JSpinner creation and are absolutely sure its editor is never changed </p>
    singulars
    1. This table or related slice is empty.
    1. POPropertyChangeSupport for SpinnerNumberModel
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USkleopatra
    1. USkleopatra
    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. 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. VTUpMod
    1. COExcellent points. My suggestion is _ad hoc_. Just as when de-normalizing a database, one must know and prepare for the consequences.
      singulars
      1. PO
      1. UStrashgod
 

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