Renamed mysql db table in development version and now it won't unlock

[Elle]

As the tile says.

I renamed the table, and while doing so my internet became unstable. Connection timed out.

Attempting rollback presents this:

I am only assuming that the name change did not fully commit and the lock is still on.

Logged into Dig Ocn to see active connections and there are none.

Anyone have an idea of what my next step should be?

Thanks so much!

~Elle

[Elle]

@George

Any idea on how I can resolve this would be very much appreciated!

~Elle

[Elle]

@Teodor

Very less than ideal, but until a more proper fix available here is what I did:

Make changes using MySQL Workbench

Delete db connection to Wappler

Re-add db connection to Wappler.

~Elle

[Hyperbytes]

Sadly the database manager is great when it works but can be a bit “fragile” when things go wrong

[Elle]

@Hyperbytes

Fragile.

Yup. That’s the word.

It’s not the end of the world - I just need to do db tables in Workbench.

I’m finding it sort of humorous the number of command syntax formatting I have to look up. There was a time - a long while ago - forming SQL statements was just part of life… I guess it’s part of my life again - for this project, anyways.

For the search engines to potentially help someone in the future searching this error, I’ll type it below since my original post is a screen shot.

Wappler Database Migration Failed due to an error! Migration table is already locked

[otavionestares]

Just found a solutions…

delete from wappler_migrations_lock

Made the migration runs!

[George]

In the next Wappler 6 beta we will be adding on option to unlock the changes history if it ever got locked:

[Teodor]

Fixed in Wappler 6 beta 15.

[Elle]

@Teodor

Excellent! Thank you!