Those of you that don't use Wappler's database manager, what do you use to sync development and production table structures?
In a Wappler website I have to access a DB that was made outside Wappler, and need some way to sync whatever table changes happen in the production DB to development, so I don't have to toy with a production DB in development...
If you use the wappler publish process it does the database update automatically at the same time.
Note sure any product can do any more than that.
What are you thinking of, db structure changes triggered by something like a development database change.
That actually sounds dangerous to me. Too much could go wrong.
I'm not sure if you understood my context, I'll try to clarify:
I have a Wappler website (project A) with its own database
I have another application (project B) with its own database
I want my Wappler website to be able to access project B database
My Wappler website doesn't perform any structure changes to project B database, so the Publish button shouldn't change any DB structure in project B
In Development, I want to clone the structure of the project B database to a local DB, to be used by my Wappler website during development
I want to repeatedly ensure my local DB schema of project B matches production's project B database, sync if needed (Sync from Production schema to Development, not the inverse)
I use DataGrip by JetBrains (a paid product). It offers connectors for a wide range of databases, and can perform comparisons between databases and can also execute schema update queries if required.
Like @brad, I use Navicat, though I've only been using it for a mere 17 years. I think you could do what you want by creating a schedule to run a job which synchronises the schema (though I haven't tried it).
phpmyadmin and navicat... as i have a WAMP server setup... and use PHP most of the time.. and i prefer connecting to the database and view the data in a separate browser window.. nice to import other data from clients sites ... as i dont always have a project setup but i always have different databases that i need to get data from..
i have made to many "crucial" mistakes when uploading my project.. publishing stuff that i should not have.... SO all manual now.. lol i know it defeats the complete point of what the Team has achieved.. BUT I DONT TRUST MYSELF........
so i always do manual update via FTP.. and run the SQL manually for updates on the live servers.....
We use replication to do this. Fail safe as only replicating remote to local. For all things remote we use Workbench or SSH directly in to the MySQL console.
Quick Google search brings up a simple script (there are plenty out there and am sure one of the LLMs could write you one specific to your needs). This script is a little old but not much changes in regards to replication so should work fine. This is remote to local but can just as easily have one instance replicate to any other (or multiple) regardless of location remote or local...
I use DBSchema for modeling etc and Postico comes in handy for every day quick mainuplation. I work with Postgres databases. Both are paid licensees. Postico is cheap onetime purchase and I purchased DBSchema perpetual years back and it is $50/year to get updated versions. I really like both of these products. For Postgres pgAdmin is also pretty good,