Change Details

I'm creating an "HR" application which essentially just synchronizes information from an external service and stores the management hierarchy of our organization in Phabricator. I don't really need to create any tables for this, I can just store edges which define the relationships between a manager and their reports. This probably subverts the way that edges are "supposed" to be used, but we try to avoid writing custom application code that writes to upstream databases wherever we can, preferring our own third party storage databases instead. This makes clarifying what is upstream managed data and internally managed data much easier. In any case, I don't seem to be able to just create a schema spec that holds edges and nothing else, unless I'm missing something?

I'm creating an "HR" application which essentially just synchronizes information from an external service and stores the management hierarchy of our organization in Phabricator. I don't really need to create any tables for this, I can just store edges which define the relationships between a manager and their reports. This probably subverts the way that edges are "supposed" to be used. Eg, I know I can just write edges into the `people` database instead, and that would actually represent the data graph correctly. However, we try to avoid writing custom application code that writes to upstream databases wherever we can, preferring our own third party storage databases instead. This makes clarifying what is upstream managed data and internally managed data much easier. In any case, I don't seem to be able to just create a schema spec that holds edges and nothing else, unless I'm missing something?

I'm creating an "HR" application which essentially just synchronizes information from an external service and stores the management hierarchy of our organization in Phabricator. I don't really need to create any tables for this, I can just store edges which define the relationships between a manager and their reports. This probably subverts the way that edges are "supposed" to be used. Eg, I know I can just write edges into the `people` database instead, and that would actually represent the data graph correctly. However, but we try to avoid writing custom application code that writes to upstream databases wherever we can, preferring our own third party storage databases instead. This makes clarifying what is upstream managed data and internally managed data much easier. In any case, I don't seem to be able to just create a schema spec that holds edges and nothing else, unless I'm missing something?