Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We use Spring's @Configurable (along with regular new operator) which works like a charm. No more <a href="http://en.wikipedia.org/wiki/Anemic_Domain_Model" rel="nofollow noreferrer">anemic domain models</a>. Finally, this is much more object oriented design, isn't it:</p> <pre><code>Person person = new Person(firstname, lastname); // weird peopleService.save(person); // good (save is @Transactional) person.save(); Mail mail = new Mail(to, subject, body); // weird mailService.send(mail); // good (send is @Transactional) mail.send(); </code></pre> <p>We haven't done any performance comparison though. So far, we simply haven't felt the need to do so.</p> <p>EDIT: that's how the person class would look like:</p> <pre><code>@Configurable("person") public class Person { private IPersonDAO _personDAO; private String _firstname; private String _lastname; // SNIP: some constructors, getters and setters @Transactional(rollbackFor = DataAccessException.class) public void save() { _personDAO.save(this); } @Transactional(readOnly = true) public List&lt;Role&gt; searchRoles(Company company) void{ return _personDAO.searchRoles(this, company); } // it's getting more interesting for more complex methods @Transactional(rollbackFor = DataAccessException.class) public void resignAllRoles(Company company) { for (Role role : searchRoles(company)) { role.resign(); } } } // the implementation now looks like this personService.getPerson(id).resignAllRoles(company); // instead of this roleService.resignAll(personService.searchRoles(personService.getPerson(id), company)); </code></pre> <p>And that's the Spring config:</p> <pre><code>&lt;context:spring-configured /&gt; &lt;bean id="person" class="org.example.model.Person" lazy-init="true"&gt; &lt;property name="personDAO" ref="personDAO" /&gt; &lt;/bean&gt; </code></pre> <p>Note: as you see, there are still services around, e.g. to search for objects (personService.getPerson(id)) but all methods that operate on a passed object (e.g. a person) are moved to that class itself (i.e. person.save() instead of personService.save(person)). The method itself stays the same and works with any underlying data access layer (pure JDBC, Hibernate, JPA, ...). It has simply moved where it belongs.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to handle injecting dependencies into rich domain models?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USsfussenegger
    1. USsfussenegger
    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. COHow do you persist your entities? Plain JDBC? Because this strategy would not work if you use hibernate!?
      singulars
      1. PO
      1. USArne
    2. CO@Arne of course it would. see my edit for an example. the idea is that you simply inject the DAO into the domain objects. Methods are then moved from services to the class (typically all methods that take an object of this class as argument). Everything else stays the same.
      singulars
      1. PO
      1. USsfussenegger
 

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