-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
yessql.db -> OrchardCore.db #7446
Conversation
IMHO yessql doesn't make sense here, seems it's copied from YesSQL repo since the beginning and no one was care about the name ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if you realise, but this breaks every orchard core installation using Sqlite.
Please don't tell me that YesSQL is using this name?!! |
AFAIK YesSQL has |
It breaks the instances already setup because they have to rename the file to the new name. |
Aha, I understand what Dean mean now If the issue is the backward compatibility we can rename the file, or just leave the current name if all agrees |
Leave current name gets my vote. Risky to try and rename files when there is no need |
Ok |
Isn't the connection string for sqlite stored in the config too? We might want to think about it, the same way it's done for other dbs, since it will also allow to set custom settings for sqlite. And that would then allow to change the name of the file. |
Reopen this to think and consider what Seb is mentioned previously this will not only allow us to rename the file, but change the database itself when it's required. I think it's a good enhancement to consider |
src/OrchardCore/OrchardCore.Data/OrchardCoreBuilderExtensions.cs
Outdated
Show resolved
Hide resolved
@sebastienros the SQLite database name is configurable now!! |
Unit Test failing. |
Oops, I didn't notice that, I will check them now ... Thanks Jasmin |
src/OrchardCore.Modules/OrchardCore.Setup/Controllers/SetupController.cs
Outdated
Show resolved
Hide resolved
src/OrchardCore/OrchardCore.Data/OrchardCoreBuilderExtensions.cs
Outdated
Show resolved
Hide resolved
src/OrchardCore.Modules/OrchardCore.Setup/Controllers/SetupController.cs
Outdated
Show resolved
Hide resolved
I faced a lot of issues in SQLiteStudio due to the name of the tenant for all the instances, I will update this PR |
This should work perfectly now!! with backward compatibility is taken in mind |
Co-authored-by: Zoltán Lehóczky <[email protected]>
Co-authored-by: Zoltán Lehóczky <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anybody else with any comments, @sebastienros @Skrypt?
As long as it is documented; it should be fine. |
Ya it's |
@hishamco this caused a problem for me. All my local site that were using Sqllite are no longer working. I think it's because it is now looking for a database named "OrchardCore" but I was using "yessql". Here is what you should do here. When creating new sites that use Sqllite, save |
I replied on the newly created issue |
This reverts commit 43a7a2d. # Conflicts: # src/OrchardCore/OrchardCore.Data.YesSql/Options/SqliteOptions.cs
) This reverts commit 43a7a2d. # Conflicts: # src/OrchardCore/OrchardCore.Data.YesSql/Options/SqliteOptions.cs
No description provided.