Closed maxachis closed 3 months ago
I'm a bit confused about this repo—if the point is to migrate regularly from production
to dev
, it seems odd that the schema and such would be defined here rather than in data-sources-app
. Would this repo make sense as a directory in data-sources-app
?
Sorry, I know you made this a week ago but I'm just now noticing.
@josh-chamberlain An excellent question!
data_sources_mirror
, which also performs regular database actions, and is maintained in its own separate repository. data_sources_app
repository would add more to an already quite sizeable repository, I could probably come up with more post-hoc rationalizations if given enough time, but those are the ones I have right now.
I don't have strong feelings on the repo, the droplet is already maintaining the full app repo for the mirror (although this will go away with the Airtable decomission). Doesn't seem too much like clutter since these are tables used by the API, but the schema definitions are not
@maxachis 1. Currently all our column names for the rest of the tables are lower case
@maxachis 1. Currently all our column names for the rest of the tables are lower case
@mbodeantor Acknowledged! Will address. In the future, may be able to automate with sqlfluff, a sql linter.
@mbodeantor I think all the status options are good
Fixes
Description
requests_v2
(likely a temporary name), which will record information related to data requests.Testing
Performance
Docs