I understand the idea of pushing the object-oriented SQL storage approach feature introducing the Catalog feature. But, please, let me (a user) to decide what tool to use to repository and store of my source code. Return back the "Save As" file menu! The current Catalog feature is build for the narrow use case and hardly used by many for the following reasons.
- The text editing (code updates and revisions) features of Aginity Pro in general are basic and lacking compared to Notepad++, Textpad, or even old Aginity.
- The small pop up-screen Preview and Edit window is a joke. You seriously think this can be useful for large hundreds of lines long SQL code scripts ?
- Fix the slowness of the pop up menus first. Read my post with video: Slow "Run query with parameters"
- Beside pure re-usable SQL, the most of the database analyst code is seldom re-usable, or used just for a lookup reference. This code is not worth saving in the Catalog. I still need it but where should I put it ?
- Accidentally closing a Tab there is no way of easy and fast recovery (unless digging deep. Why?)
- The code is locked in the Aginity Tool. What if I loose my computer or disk ?
The shortcomings and deficiencies the new Aginity Pro come at user expense:
- Copy/paste source code saving it in the text editor for later and long term use.
- Toggling (copy/paste) back/forth between a text editor (save and edit) and Aginity Pro to run the code.
I'm keeping my own repository structure in files. If interested, I can share with you what I do for a repository, so you may lean a thing, or two about how efficiently store a silos of source code for the database (not programming, yo!) coding works.
Observe, the back end database coding is different than conventional programming paradigms.
Please sign in to leave a comment.