Databases
StackOverflow2013
Usersdbo
USMax_B
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USMax_B
    primarykey
    data
    text
    plurals
    1. POHow to force UNIDIRECTIONAL to-many relationship to persist
      singulars
      1. PTQuestion
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to support both armv6 and armv7s for release build in xcode 4.5
      1. USMax_B
      1. VTFavorite
    2. VO
      singulars
      1. POHow to force UNIDIRECTIONAL to-many relationship to persist
      1. USMax_B
      1. VTBountyStart
    3. VO
      singulars
      1. POHow to force UNIDIRECTIONAL to-many relationship to persist
      1. USMax_B
      1. VTFavorite
    1. COI do model bidirectional from the join table to employee, I have a unidirectional to-one from join entity to department. My usage, not the employees stuff, is more of filesystem/cache management kind. There are tens of thousands of items in several (not much) overlapping sets. The current version is using inverse relationship. The performance drop is obvious as the number of managed items raises. Loading a 50000 items set just to add one is not optimal, when adding the item is done by adding one entry in two tables. The new, work in progress, join entity model is better. No huge set loading.
      singulars
      1. PO
      1. USMax_B
    2. COI still don't get **why** CoreData framework is not able to generate and update join table on unidirectional many2many. Or, even better, stays with the inverse relationship requirement but **not to load the full set to update an inverse relationship when it only needs to update a few entries in the join table**
      singulars
      1. PO
      1. USMax_B
    3. COI have implemented the joining entity solution on a branch of my code. It works as expected. It is not optimal since the joining entity table is twice as large as the automatically generated joining table (+ Z_PK and Z_ENT). The code is less clean but not much. The only real drawback is that it is now less easy to brake retain cycles. In the normal dept/empl, if you add/modify a bunch of employees, you just need to refault the dept after the save to get rid of employees entities. Now you need to iterate on employees to refault each one which has a retain cycle with its joining entity.
      singulars
      1. PO
      1. USMax_B
 

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