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.

Sign up for GitHub

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

Jump to bottom

Bring back SQLite #1953

Closed
bricelam opened this issue Mar 30, 2015 · 5 comments
Closed

Bring back SQLite #1953

bricelam opened this issue Mar 30, 2015 · 5 comments
Assignees
@bricelam
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone
1.0.0

Comments

@bricelam
Copy link
Contributor

No description provided.

@bricelam bricelam self-assigned this Mar 30, 2015
@ErikEJ
Copy link
Contributor

ErikEJ commented Mar 31, 2015

Yir!

@rowanmiller rowanmiller added this to the 7.0.0 milestone Apr 20, 2015
@bricelam bricelam modified the milestones: 7.0.0, 7.0.0-beta5 Apr 28, 2015
@crozone
Copy link

crozone commented May 12, 2015

Any word on SQLite migrations?

@ErikEJ
Copy link
Contributor

ErikEJ commented May 12, 2015

@crozone They work, you must invoke programatically on Windows Phone and Store apps. What are you looking for?

@crozone
Copy link

crozone commented May 12, 2015

I'm trying to apply migrations in an ASP.NET 5 application, using dnx . ef migration apply or Database.AsRelational().ApplyMigrations() from within the DbContext.

This appears to require methods within Microsoft.Data.Entity.Sqlite.Migrations.SqliteHistoryRepository which are not yet implemented:

https://github.com/aspnet/EntityFramework/blob/dev/src/EntityFramework.Sqlite/Migrations/SqliteHistoryRepository.cs

Is there another way to apply or invoke the migrations?

@bricelam
Copy link
Contributor Author

@crozone Sorry, Migrations had changed a lot so it needs to be re-implemented.

@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Oct 15, 2022
@ajcvickers ajcvickers modified the milestones: 1.0.0-beta5, 1.0.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bricelam bricelam

Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
5 participants
@bricelam @ajcvickers @crozone @ErikEJ @rowanmiller