Devart Forums

I'm evaluating MySQL stored proc/func development tools at the moment and I've a hunch that dbForge might be the best one I've used so far.
I want to manage my stored procs (etc) in external files as they're under git version control - that is to say, I do not want to log on to my database and start editing code that's already inside the database - I want to log on to the database and then open and 'compile' an external SQL file as that would always be considered the point of truth.
How can I go about this in dbF? It lends itself to opening SQL files (good start) but doesn't know to interpret them as stored procs. There's no 'open a stored proc' option other than directly from the database, so far as I can see. Am I mistaken?

Thanks.

Could you please describe in more detail the result you are intending to achieve with dbForge and let us know what you mean by "'open a stored proc"?

Sure. In all other software development work I use some form of version control (as does everyone in the modern era). Because of this I have a set of source files that I checkout, edit, compile, commit, that kind of thing. Using Eclipse, SQL Developer (unless avoidable), PL/SQL Developer, Nebeans, whatever, those files sit outside the target environment. For MySQL I need SQL files to work this way. That means I need to checkout from my VCS, edit, 'compile' (to the database), save on my local disk, commit back to VCS. dbForge doesn't seem to encourage this behaviour. It seems to encourage editing code that's already in the database and then saving it to a flat file if necessary. There's no workflow I can discern that allows/encourages version controlled source files checked-out on local disk.

This doesn't seem to be specific to dbForge, BTW, I've tried a couple of other MySQL development tools and they also seem to want the database to be the point of truth rather than the VCS.

Maybe I'm missing the point?

Thank you for the reply.

You can add a suggestion on our UserVoice forum where other users can vote for it http://devart.uservoice.com/forums/7729 ... -for-mysql

We collect and analyze the information from this forum in order to make a proper roadmap for future product releases.

Also, we are planning to implement in one of the next product versions a feature similar to https://www.devart.com/dbforge/sql/source-control/

Alexa, thanks for taking the time to reply