Skip to main content
Updated the body of question and added the specific tag of the database management system of relevance.
Source Link
Stephen Rauch
  • 4.3k
  • 12
  • 24
  • 36

I'm developing a system that supports creating accounts and multiple users within every account that can each access a certain subset of data of their "parent" account. The

The data is stored in a SQL Server database in the following tables:

Folders: 
Id(guid, primary key), Name(nvarchar(200)), AccountId(guid, foreign key)), ParentFolderId(guid, foreign key) 
Files: 
Id(guid, primary key), Name(nvarchar(200)), FolderId(guid, foreign key), 
UserFolderPermissions: 
Id(guid, primary key), FolderId(guid, foreign key), UserId(guid, foreign key)
  • Folders: Id(guid, primary key), Name(nvarchar(200)), AccountId(guid, foreign key)), ParentFolderId(guid, foreign key)

  • Files: Id(guid, primary key), Name(nvarchar(200)), FolderId(guid, foreign key),

  • UserFolderPermissions: Id(guid, primary key), FolderId(guid, foreign key), UserId(guid, foreign key)

I'm developing a system that supports creating accounts and multiple users within every account that can each access a certain subset of data of their "parent" account. The data is stored in a SQL Server database in the following tables:

Folders: 
Id(guid, primary key), Name(nvarchar(200)), AccountId(guid, foreign key)), ParentFolderId(guid, foreign key) 
Files: 
Id(guid, primary key), Name(nvarchar(200)), FolderId(guid, foreign key), 
UserFolderPermissions: 
Id(guid, primary key), FolderId(guid, foreign key), UserId(guid, foreign key)

I'm developing a system that supports creating accounts and multiple users within every account that can each access a certain subset of data of their "parent" account.

The data is stored in a SQL Server database in the following tables:

  • Folders: Id(guid, primary key), Name(nvarchar(200)), AccountId(guid, foreign key)), ParentFolderId(guid, foreign key)

  • Files: Id(guid, primary key), Name(nvarchar(200)), FolderId(guid, foreign key),

  • UserFolderPermissions: Id(guid, primary key), FolderId(guid, foreign key), UserId(guid, foreign key)

Updated the body of question and added the specific tag of the database management system of relevance.
Source Link

I'm developing a system that supports creating accounts and multiple users within every account that can each access a certain subset of data of their "parent" account. The data is stored in a SQL Server database in the following tables: Accounts: Id(guid, primary key), Title(nvarchar(200)), Users: Id(guid, primary key), Login(navrchar), AccountId(guid, foreign key).

  • Accounts: Id(guid, primary key), Title(nvarchar(200))
  • Users: Id(guid, primary key), Login(nvarchar), AccountId(guid, foreign key).

I'm developing a system that supports creating accounts and multiple users within every account that can each access a certain subset of data of their "parent" account. The data is stored in a SQL Server database in the following tables: Accounts: Id(guid, primary key), Title(nvarchar(200)), Users: Id(guid, primary key), Login(navrchar), AccountId(guid, foreign key).

I'm developing a system that supports creating accounts and multiple users within every account that can each access a certain subset of data of their "parent" account. The data is stored in a SQL Server database in the following tables:

  • Accounts: Id(guid, primary key), Title(nvarchar(200))
  • Users: Id(guid, primary key), Login(nvarchar), AccountId(guid, foreign key).
Tweeted twitter.com/StackCodeReview/status/1054115108090191872
added 103 characters in body
Source Link

Now, I need to implement a concept of "Folders" and "Files" within accounts. Each account can have a number of files (an object with a name and a few other non significant properties) that can be arranged into folders (like a file system), and every user might have a permission to access a folder. "A user has permission to view a folder" means that this user can see all files within this folder and within all its subfolders. These folders/files also have to support a lot of moving around the hierarchy, renaming, editing, etc.

Now, I need to implement a concept of "Folders" and "Files" within accounts. Each account can have a number of files (an object with a name and a few other non significant properties) that can be arranged into folders (like a file system), and every user might have a permission to access a folder. "A user has permission to view a folder" means that this user can see all files within this folder and within all its subfolders.

Now, I need to implement a concept of "Folders" and "Files" within accounts. Each account can have a number of files (an object with a name and a few other non significant properties) that can be arranged into folders (like a file system), and every user might have a permission to access a folder. "A user has permission to view a folder" means that this user can see all files within this folder and within all its subfolders. These folders/files also have to support a lot of moving around the hierarchy, renaming, editing, etc.

Source Link
Loading