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

IsSqlServer etc migrationBuilder extensions #16956

Merged
merged 1 commit into from
Aug 13, 2019
Merged

IsSqlServer etc migrationBuilder extensions #16956

merged 1 commit into from
Aug 13, 2019

Conversation

xaviergxf
Copy link

@xaviergxf xaviergxf commented Aug 5, 2019

Migrations: Add IsSqlServer, etc. to MigrationBuilder

Fixes #8566

@xaviergxf xaviergxf requested a review from dougbu as a code owner August 5, 2019 15:42
@dnfclas
Copy link

dnfclas commented Aug 5, 2019

CLA assistant check
All CLA requirements met.

@bricelam
Copy link
Contributor

bricelam commented Aug 5, 2019

(Rebased on top of release/3.0)

/// <param name="migrationBuilder"> The migrationBuilder from the parameters on <see cref="Migration.Up(MigrationBuilder)" /> or <see cref="Migration.Down(MigrationBuilder)" />. </param>
/// <returns> True if SQL Server is being used; false otherwise. </returns>
public static bool IsSqlServer([NotNull] this MigrationBuilder migrationBuilder)
=> migrationBuilder.ActiveProvider.Equals(
Copy link
Contributor

Choose a reason for hiding this comment

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

ActiveProvider may be null. Best to use the static string.Equals()

Copy link
Author

Choose a reason for hiding this comment

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

Done :)

@bricelam bricelam self-assigned this Aug 5, 2019
@dougbu
Copy link
Member

dougbu commented Aug 5, 2019

@bricelam this cannot be merged until the license bot is satisfied

@bricelam
Copy link
Contributor

bricelam commented Aug 5, 2019

@dougbu I'm aware

@xaviergxf
Copy link
Author

(Rebased on top of release/3.0)

How do i know when to target master or release/x.0?

@bricelam
Copy link
Contributor

How do i know when to target master or release/x.0?

Start on the repo's default branch (currently release/3.0). It changes depending on how close we are to releasing or how soon we start working on the next release.

@bricelam bricelam merged commit 29b269a into dotnet:release/3.0 Aug 13, 2019
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.

5 participants