Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Have a look to <a href="http://docs.oracle.com/javase/tutorial/uiswing/events/propertychangelistener.html" rel="nofollow">http://docs.oracle.com/javase/tutorial/uiswing/events/propertychangelistener.html</a></p> <pre><code>public class Test { PropertyChangeSupport pcs = new PropertyChangeSupport(this); private String name; private int age; public String getName() { return name; } public void setName(String name) { String oldName = this.name; this.name = name; pcs.firePropertyChange("name", oldName, name); } public int getAge() { return age; } public void setAge(int age) { int oldAge = this.age; this.age = age; pcs.firePropertyChange("age", oldAge, age); } public void addPropertyChangeListener(PropertyChangeListener listener) { pcs.addPropertyChangeListener(listener); } public void removePropertyChangeListener(PropertyChangeListener listener) { pcs.removePropertyChangeListener(listener); } public Test(){ } public static void main (String[] args){ Test myTestObject = new Test(); myTestObject.addPropertyChangeListener(new MyPropertyChangeListener()); myTestObject.setAge(12); myTestObject.setName("Rick"); myTestObject.setName("Andrew"); } private static class MyPropertyChangeListener implements PropertyChangeListener { @Override public void propertyChange(PropertyChangeEvent event) { String clazz = event.getSource().getClass().getName(); System.out.println(clazz+"::"+event.getPropertyName()+" changed from "+event.getOldValue()+" to "+event.getNewValue()); } } } </code></pre> <p>This is a simple example but using this approach you can create different PropertyChangeListeners and provide different logic inside theirs method propertyChange. Also is possible to fire only the changes over a small set of attributes and not over all of them (not storing the oldValue and not firing the firePropertyChange method of PropertyChangeSupport).</p> <p>Of course that you can use AOP, but perhaps you are looking for a solution like presented above. I hope this helps. </p>
    singulars
    1. This table or related slice is empty.
    1. POkeep track of an instance attributes changes
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USsgroh
    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. VTDownMod
    1. COPropertyChangeListener is not a remote interface, so this suggestion cannot possibly work.
      singulars
      1. PO
      1. USuser207421
    2. COHi @EJP, I understand your point. Assuming that we are trying to mitigate the amount of information that will be send. Assuming that you need to update clients with information that changed in the server; one solution could be send only the changes detected: At server side, use the code proposed and add another class implementing the Remote interface, provide a getChanges method and return a List<Changes> (that will be created with the code proposed above). The Client finally will process the List, using the changes according the project needs. Please let me know if I was not clear.
      singulars
      1. PO
      1. USsgroh
    3. CO@MBZ, did the answer helps you? Please let me know if my post was enough or I need to update it with the comments that I post on Oct 23.
      singulars
      1. PO
      1. USsgroh
 

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