Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cigrid-ui-412 new column types #74

Merged
merged 7 commits into from
May 16, 2023

Conversation

islean
Copy link
Contributor

@islean islean commented May 12, 2023

Changed

  • New alembic script to alter column types (to be added)
  • New type hints in the Python models

Steps to consider while deploying

  • Configuration changes:
  • Documentation updates:
  • Inform users by email:

Review:

  • Code approved by
  • Tests executed on stage by: (Document the test done with screen shots and description.)
  • "Merge and deploy" approved by

This version is a:

  • MAJOR - when you make incompatible API changes
  • MINOR - when you add functionality in a backwards compatible manner
  • PATCH - when you make backwards compatible bug fixes or documentation/instructions

@clingen-sthlm clingen-sthlm temporarily deployed to stage May 16, 2023 07:00 Inactive
@clingen-sthlm clingen-sthlm temporarily deployed to stage May 16, 2023 07:25 Inactive
@islean
Copy link
Contributor Author

islean commented May 16, 2023

Tested in stage and the backend seemed to allow for strings as method document + method version. Attaching screenshot:

Screenshot 2023-05-16 at 09 38 44

@islean islean marked this pull request as ready for review May 16, 2023 09:00
Copy link
Contributor

@ChrOertlin ChrOertlin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks mainly like formatting, and some table changes.

Seems the alembic downgrade reverses everything introduced by the upgrade in case it is needed.

Looks good!

op.alter_column("user", "email", existing_type=mysql.VARCHAR(length=128), nullable=False)
op.drop_index("email", table_name="user")
op.drop_index("google_id", table_name="user")
op.create_index(op.f("ix_user_email"), "user", ["email"], unique=True)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just for me to understand, this makes a link between user, email and then generates an index over that?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It creates and index for the email column in the user table

@islean islean merged commit 5e8a9fc into main May 16, 2023
@islean islean deleted the cigrid-ui-412-wrong-types-in-plate-sign-off branch May 16, 2023 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants