-
Notifications
You must be signed in to change notification settings - Fork 317
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
Upgrading from 2.x to 3.x documentation #270
Comments
Hi, The underlying DreamFactory system database is different from the MySQL connector. MySQL will still work fine as the system database for DreamFactory 3, and there is no known reason why that will ever change. Incidentally, other system databases are also supported, including SQLite, PostgreSQL, and Microsoft SQL Server. Jason |
I hate this decision they removed pre and post scripts processing from open source version.
Thanks,
Sree
Sent from my iPhone, please ignore if there are any typos.
On Sep 26, 2019, at 2:24 PM, Todd Appleton <[email protected]> wrote:
Hi,
The underlying DreamFactory system database is different from the MySQL connector. MySQL will still work fine as the system database for DreamFactory 3, and there is no known reason why that will ever change. Incidentally, other system databases are also supported, including SQLite, PostgreSQL, and Microsoft SQL Server.
Jason
On September 26, 2019 at 2:11:54 PM, tvarsis ([email protected]) wrote:
Since MySQL is removed from the opensource version in version 3.0, and all users are stored in MySQL as the default storage, I guess we will have to migrate that to SQLite that is the new default storage for config and DF users. But there are no documentation at all about upgrading from 2.x -> 3.x, nor any release notes in the Wiki for 3.x.
Are there more breaking changes or things to consider when upgrading? Is the upgrade process automatic? Database migrations moving from MySQL to SQLite and so on?
Documentation about this is really required.
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#270?email_source=notifications&email_token=AA23GEQE3CSKMC55OELRZ5TQLUD75A5CNFSM4I25K3P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7WWCWQ#issuecomment-535650650>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AA23GESRT44BOMZZDAG3MCTQLUD75ANCNFSM4I25K3PQ>.
|
Thanks for the information! So does this mean the upgrade to version 3 will work the same way as a minor 2.x upgrade? Are there any caveats other than losing support for MySQL/Mongo/scripts? I'm using docker compose from your docker hub with version 2.14.2 |
Since MySQL is removed from the opensource version in version 3.0, and all users are stored in MySQL as the default storage, I guess we will have to migrate that to SQLite that is the new default storage for config and DF users. But there are no documentation at all about upgrading from 2.x -> 3.x, nor any release notes in the Wiki for 3.x.
Are there more breaking changes or things to consider when upgrading? Is the upgrade process automatic? Database migrations moving from MySQL to SQLite and so on?
Documentation about this is really required.
Thanks!
The text was updated successfully, but these errors were encountered: