Skip to content
← dbForge Studio for MySQL

I suggest you...

dbForge Studio for MySQL: Bugs

Categories

JUMP TO ANOTHER FORUM

(thinking…)

I need posibility to run SQL not SQL files only.

SQL code saved in file with "config" extension cannot be executed. Can you redefine this ? I need posibility to run SQL not SQL files only.

2 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Victor Dereveanschi shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Alexey Stepanov commented  ·   ·  Report

    This bug was originally submitted for dbForge Studio for PostgreSQL, why now it related to "dbForge Studio for MySQL"?

  • Alexey Stepanov commented  ·   ·  Report

    +1. We have thousands legacy files in our version control sysem with extensions other than ".sql" (e.g. ".viw",".tab",".udf",".trg"). This legacy extensions originated in SQL Server Enterprise Manager and was kept after migration to PostgreSQL.

    Please add ability to configure file extensions.