Feature Request – Flexible .sql File Extension and Folder Structure in “Export User Objects”

[adrian_star]

Hello,

I would like to submit a feature request regarding the “Export User Objects” module in PL/SQL Developer.

Currently, when exporting objects using the File per object option, the generated files may use object-type-specific extensions (e.g. .trg, .vw, .pck, .tps, etc.), depending on configuration and version.

In our development workflow, we require all database objects to be exported strictly as .sql files. This is important because:

• All scripts are version-controlled in Git.
• Files are processed by CI/CD pipelines (Jenkins).
• Each file contains Liquibase headers used for automated deployments.
• Our internal standards enforce a uniform .sql extension across all database objects.

While the “Single file” option produces a .sql script, we need a File per object export that:

1. Always generates files with a .sql extension.
2. Optionally groups objects into subdirectories based on object type (e.g., tables/, views/, packages/, triggers/).

This would be similar to the behavior of the Database Export feature in Oracle SQL Developer, where objects are automatically organized into type-based subfolders and exported as .sql files.

Such functionality would significantly improve integration with modern DevOps workflows and source control systems.

Suggested enhancements:

• Explicit setting: “Force .sql extension for all object types”.
• Optional directory structure by object type.
• Optional template header support (for Liquibase compatibility).

This improvement would make PL/SQL Developer more aligned with CI/CD-oriented database development practices.

Thank you for considering this request.

Best regards,
Adrian

 

[Marco Kalter]

Thank you for your feedback. I have added this to the list of enhancement requests.