Hi,
Loving the workset facility - it helps me gather the set of files I use for particular pieces of work within the application together with useful SQL for that work.
One thing I am finding annoying, though, is a knock-on from a workflow I use for managing patch releases: the patch files are moved from an "inprocess" folder to the parent folder when the patch is released. Returning to a workset which referenced one of the files that is now released pops up a message (correctly) saying the file doesn't exist - for each file moved. It's not just moving the file from "inprocess", it will be "patches/inprocess/patch42/file23.sql" to "patches/patch42/file23.sql".
This slows down the opening of the workset somewhat and I was wondering if something could be looked at or suggested to mitigate it.
For example, one or more of:
- Don't open those windows and, instead, once the workset is open pop up a message listing the files that could not open
- Add a 'don't show again' checkbox to the "missing file" dialogue
- Add a "content management" facility to worksets to allow the listing of files and flagging of those that are missing
- Add an option to search for missing files when they fail to open
- Some other idea that's easier to deliver (or already in mind!) that I haven't thought of
- Some other idea from this forum that might turn out to be better, easier to deliver and/or resolve a problem for someone else, too
I could, of course, revise my workflow to avoid this problem - but where's the fun in that?
Thanks,
Tim
Loving the workset facility - it helps me gather the set of files I use for particular pieces of work within the application together with useful SQL for that work.
One thing I am finding annoying, though, is a knock-on from a workflow I use for managing patch releases: the patch files are moved from an "inprocess" folder to the parent folder when the patch is released. Returning to a workset which referenced one of the files that is now released pops up a message (correctly) saying the file doesn't exist - for each file moved. It's not just moving the file from "inprocess", it will be "patches/inprocess/patch42/file23.sql" to "patches/patch42/file23.sql".
This slows down the opening of the workset somewhat and I was wondering if something could be looked at or suggested to mitigate it.
For example, one or more of:
- Don't open those windows and, instead, once the workset is open pop up a message listing the files that could not open
- Add a 'don't show again' checkbox to the "missing file" dialogue
- Add a "content management" facility to worksets to allow the listing of files and flagging of those that are missing
- Add an option to search for missing files when they fail to open
- Some other idea that's easier to deliver (or already in mind!) that I haven't thought of
- Some other idea from this forum that might turn out to be better, easier to deliver and/or resolve a problem for someone else, too
I could, of course, revise my workflow to avoid this problem - but where's the fun in that?
Thanks,
Tim
