if you want to look up "what permissions does user X have on asset Y"
then i would model that as a row keyed by userid, containing
supercolumns named by asset ids, and containing subcolumns of the
permissions granted.
On Mon, Apr 19, 2010 at 12:03 PM, tsuraan wrote:
> Suppose I have a CF that hol
> It seems to me you might get by with putting the actual assets into
> cassandra (possibly breaking them up into chunks depending on how big
> they are) and storing the pointers to them in Postgres along with all
> the other metadata. If it were me, I'd split each file into a fixed
> chunksize an
On Tue, Apr 20, 2010 at 1:37 PM, tsuraan wrote:
> The assets are binary files on a document tracking system. Our
> current platform is postgres-backed; the entire system we've written
> is fairly easily distributed across multiple computers, but postgres
> isn't. There are reliable databases tha
> I'm curious as to how you would have so many asset / user permissions that
> you couldn't use a standard relational database to model them. Is this some
> sort of multi-tenant system where you're providing some generalized asset
> check-out mechanism to many, many customers? Even so, I'm not sure
The short answer as to what people normally do is that they use a
relational database for something like this.
I'm curious as to how you would have so many asset / user permissions that
you couldn't use a standard relational database to model them. Is this some
sort of multi-tenant system w
> Suppose I have a CF that holds some sort of assets that some users of
> my program have access to, and that some do not. In SQL-ish terms it
> would look something like this:
>
> TABLE Assets (
> asset_id serial primary key,
> ...
> );
>
> TABLE Users (
> user_id serial primary key,
> user_n
Suppose I have a CF that holds some sort of assets that some users of
my program have access to, and that some do not. In SQL-ish terms it
would look something like this:
TABLE Assets (
asset_id serial primary key,
...
);
TABLE Users (
user_id serial primary key,
user_name text
);
TABLE
