Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POParent/child model for DTO
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBRPocock
    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
    1. COPardon me for the late reply. Thanks for replying. Wouldn't this put two unrelated types in the same inheritance tree? Still, if a method is to return a Person, it would now be returning a PersonResolver, right? So it would have to be casted back to the required type for proper use, right?
      singulars
      1. PO
      1. UShkansal
    2. COThe idea here is, to store only PersonResolver types. A Person can then be resolved to itself (`Person a; a.resolvePerson() == a`), whereas your ResourceLink type would resolve to the person it links (`ResourceLink b; b.resolvePerson() == (Person)b.getTargetOfLink()`). — This allows the use of containers like `List<PersonResolver>` by allowing all of the children to yield a `Person` orthogonally, rather than `if (x instanceof Person)` and the like. As for “inheritance tree,” it's just an interface — it *makes* the types to be related; versus putting two unrelated types into a single container…
      singulars
      1. PO
      1. USBRPocock
    3. COso a `Person` would have to have a PersonResolver, which could refer to either a `Person` or `ResourceLink` and we don't care what it is, as it'll be taken care of at runtime. I'm not happy with the *IsA* thing here, as I was looking for something more *HasA* types. But I'm thankful to you for taking time and answering. I'll mark it as accepted as I had, unfortunately, myself thought of an interface, without the resolver thing; but don't want to relate unrelated objects. Thanks!
      singulars
      1. PO
      1. UShkansal
 

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