Bug 197729 - [ews-app] Add migrations file to repository
Summary: [ews-app] Add migrations file to repository
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Aakash Jain
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-05-08 18:09 PDT by Aakash Jain
Modified: 2019-05-09 10:27 PDT (History)
8 users (show)

See Also:


Attachments
Patch (3.97 KB, patch)
2019-05-09 03:53 PDT, Aakash Jain
no flags Details | Formatted Diff | Diff
Archive of layout-test-results from ews213 for win-future (13.39 MB, application/zip)
2019-05-09 05:40 PDT, EWS Watchlist
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aakash Jain 2019-05-08 18:09:24 PDT
As per https://docs.djangoproject.com/en/1.11/topics/migrations/ "The migration files for each app live in a “migrations” directory inside of that app, and are designed to be committed to, and distributed as part of, its codebase."

We should add the migration file for ews-app to the repository. That would make it easier to reproduce the environment consistently, and also make it easier to track schema changes.
Comment 1 Aakash Jain 2019-05-09 03:53:12 PDT
Created attachment 369483 [details]
Patch
Comment 2 EWS Watchlist 2019-05-09 05:40:19 PDT Comment hidden (obsolete)
Comment 3 EWS Watchlist 2019-05-09 05:40:21 PDT Comment hidden (obsolete)
Comment 4 Jonathan Bedard 2019-05-09 08:47:38 PDT
I agree that committing this is a good idea, but only if we're at a point where the schema is expected to be mostly stable, are we at that point?

To be clear, I'm am expecting future schema changes, but I'm not expecting us to be iterating on the entire architecture of the EWS app.
Comment 5 Aakash Jain 2019-05-09 09:02:34 PDT
(In reply to Jonathan Bedard from comment #4)
> I agree that committing this is a good idea, but only if we're at a point where the schema is expected to be mostly stable, are we at that point?
Yup. I think we are at that point. I have been holding this off for a while for this reason. Haven't had any schema change for over a month.

Also since we have already deployed in production, Django will create separate incremental migration file for any further schema change on the production server. Therefore it's best to check-it in to keep any testing environment similar to production environment.
Comment 6 WebKit Commit Bot 2019-05-09 10:13:53 PDT Comment hidden (obsolete)
Comment 7 Aakash Jain 2019-05-09 10:26:13 PDT
Comment on attachment 369483 [details]
Patch

Clearing flags on attachment: 369483

Committed r245143: <https://trac.webkit.org/changeset/245143>
Comment 8 Aakash Jain 2019-05-09 10:26:16 PDT
All reviewed patches have been landed.  Closing bug.
Comment 9 Radar WebKit Bug Importer 2019-05-09 10:27:25 PDT
<rdar://problem/50626696>