Databases
StackOverflow2013
Usersdbo
USAndy Etheridge
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USAndy Etheridge
    primarykey
    data
    text
    plurals
    1. PO
      singulars
      1. PTAnswer
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COInstead of doing it this way, could you throw away your Relationship entity and instead just create instances of ClassA and ClassB and link them together via their relationship? You could add an attribute to these entities to indicate that it is placeholder instead of a fully populated entity?
      singulars
      1. POEfficient CoreData fetches using subqueries
      1. USAndy Etheridge
    2. COIf the keywords are common to multiple CHECKLISTs then use a many-to-many relationship. In this case there would only be a single KEYWORD entity with a property of "marty" and it would have a relationship to each CHECKLIST that has "marty" in the normalisedName. This way you are searching a smaller number of entities. If common keywords are rare then don't bother with the KEYWORDS entity, just use your normalisedName field. You might want to include a space at the start and end of this field so that you can to startswith style searches by prepending a space to the search text.
      singulars
      1. POCore Data - relationships or attributes?
      1. USAndy Etheridge
    3. COCould you give an example of the strings that are actually stored in KEYWORDS for a particular CHECKLIST. Would different CHECKLISTs ever have the same search keys words? I am wondering whether your relationship should be many-to-many with each KEYWORD record containing a single word? E.g. a search for "wibble" would return a single KEYWORD that has relationship to all CHECKLISTs that match this search. This would make the search more efficient if the number of KEYWORDS is much less than the number of CHECKLISTS. Whether this is the case or not will depend on your data.
      singulars
      1. POCore Data - relationships or attributes?
      1. USAndy Etheridge
 

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