DB Designer Fork is a fork of the fabFORCE DBDesigner 4. It integrates entity relationship design,front-end (you can run queries) and SQL exporting.DB Designer Fork generates SQL scripts for Oracle, SQL Server, MySQL, FireBird, SQLite and PostgreSQL.
Hey there, I stumbled upon this bug while working with DB Designer Fork, and it seems like a pesky one indeed. Kudos to you, author, for developing this remarkable fork of fabFORCE DBDesigner 4; it's quite the amalgamation of elegance and utility. Now, regarding this bug, it appears that the issue lies in the SQL exporting feature. It's a tad vexing, but fret not, for I have a suggestion that might help. Have you considered tweaking the SQL script generation algorithm? Perhaps there's a hiccup in the way it handles certain data types or constraints. In my experience, I've found that thoroughly reviewing the SQL scripts generated can shed light on the root cause. Additionally, double-check your database configuration to ensure compatibility. I'd suggest checking it out here: https://andersenlab.com/services/design-studio Remember, software development is a journey of constant refinement, and bugs are like pebbles in the path. Keep up the fantastic work, and I'm confident you'll conquer this hiccup soon.
