Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've just been implementing something similar (REALbasic talking to MySQL) over the last couple of weeks for a hierarchical multi-company extension to an accounting package.</p> <p>There's a large body of existing code which composes SQL statements so we had to live with that and just do a lot of auditing to ensure the restrictions were included in each table as appropriate. One gotcha was <em>related lookups</em> where lookup tables were normally only used in combination with a primary table but for some maintenance GUIs would load the lookup table itself, directly.</p> <p>There's a danger of giving away implied information such as revealing that Acme Pornstars are a client of some division of the company ;-)</p> <p>The only solution for that part was very careful construction of DB diagrams to show all implied relationships and lots of auditing and grepping source code, with careful commenting to indicate areas which had been OK'd as not needing additional restrictions.</p> <p>The one pattern I've come up with to make this more generalised in future is, rather than explicit region=currentRegionVar type searches, using an arbitrary entityID which is supplied by a global CurrentEntityForRole("blah") function.</p> <p>This abstraction allows for sharing of some data as well as implementing pseudo-entities which represent other restriction boundaries.</p> <p>I don't know enough about Java and Spring to be able to tell but is there a way you could use views to provide a single-key lookup, where the views are restricted by the region filter?</p> <p>The desire to provide aggregations and possible data sharing was why we didn't go down the separate database route.</p>
    singulars
    1. This table or related slice is empty.
    1. POhow to restrict or filter database access according to application user attributes
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAndy Dent
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POhow to restrict or filter database access according to application user attributes
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    1. COi'm coming to the same conclusion... I'm just going to have to capture all direct/indirect SQL statements. could you expand a touch on how you use your CurrentEntityForRole() function - I'm not quite sure I understand?
      singulars
      1. PO
      1. USCorin Fletcher
    2. CO"WHERE accounts.corpEntityID=" + CorporateEntities.IDforRoleQuoted("accounts") allows for a different entity instead of the current user's. Say companies and divisions share chart of accounts - a division gets its parent company's ID. It maps CurrentID+Role => effectiveID. Rarely used but useful.
      singulars
      1. PO
      1. USAndy Dent
 

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