I see a message "Migrate your plugin to a V2 database", but don't know what that is
I have googled for it, searched in Railway help, searched in KB, can't find any docs. Would be really nice if there was a link to docs right there inside the "Migrate your plugin to a V2 database" message, so people know what it is.
I'm afraid to click the button, for fear of something breaking, or losing features that I currently enjoy in my current config.
35 Replies
Project ID:
N/AN/A
Hi @VoiceOfSoftware
Clicking that button will open up a modal that will explain what will happen. You can also view the guide here https://docs.railway.app/guides/database-migration-guide
That is good feedback about having a link right in the banner though!
Yes, a button named [Migrate] makes it seem like something is going to happen right away...there's no indication that it's going to present a dialog. Perhaps [Learn More About Migrating]
@jr after migration, my stored procedures don't seem to exist, at least not the way I was calling them before: PROCEDURE railway.GetCalendarBroadcasts does not exist
project b855592c-9156-4020-9543-d41a4e939fde
You mean the MySQL procedures?
MySQL stored procedures, yes
[0] code: 'ER_SP_DOES_NOT_EXIST',
[0] errno: 1305,
[0] sql: "CALL WorksQuery('devas','',false)",
[0] sqlState: '42000',
[0] sqlMessage: 'PROCEDURE railway.WorksQuery does not exist'
let me take a look
the data from the plugin was not removed so the migration might just need to be updated
Seems like the stored procedures exist (when I connect directly to MySQL with TablePlus client), but my NodeJS mysql2 package seems to be unable to call them
Is it this deployment that you are referring to? https://railway.app/project/b855592c-9156-4020-9543-d41a4e939fde/service/77633db6-7ea1-4ef3-9f4a-c12b733ad491?id=965b0312-4d70-4e2a-8410-a3b50b803a5e
Yes, that's my prod environment, and I also have a dev environment that's failing
Oh, my TablePlus may be hitting the old MySQL environment?
OK, now that I'm hitting the new MySQL database, I see no stored procedures there any more
I see I see. I think there may be 2 issues here.
1. You are running into the network initialization issue. To fix this you can add a
sleep 2 && <actual start command> in the package.json start script
2. MySQL routines and procedures were not successfully restored. This is a simple fix that we can do to update the MySQL migration script.Will you be able to migrate the stored procedures for me?
Yes, once the migration script is updated, you can delete newly created "MySQL" service and re-run the migration
I'll let you know once that is good to go
For startup, do you mean this line in package.json?
"start": "node build/index.js",
"start": "sleep 2 && node build/index.js",
Yeah. Can you change it to
yeah perfect