Scripting ignores procedure

• 
  Stephen, thank you for your forum post.
  
  I have been able to recreate the problem you are experiencing and will raise a Bug Report for this issue. This report will then be brought to the attention of our developers.
  
  Once I recieve a reply I will update you. I have created a support call and the reference is F0009734
  
  Many Thanks
  
  Matt
  
  Matthew Flatt
  Technical Support Engineer
  Red-Gate Software Ltd
  support@red-gate.com

  Matthew Flatt January 25, 2008 06:45

  - 0 +
• 
  We are looking into the best way to alert users to objects in script files that our parser cannot deal with (which is what is causing your problem).
  
  Currently, SQL Compare just ignores such areas of a script file, because there are many legitimate reasons to have non-parsable sections in the script file (e.g. database creation code, data handling, transactions, error handling) and we felt it was best to just read in what we could, to allow customers as much flexibility as possible in what could be contained in a readable script database file.
  
  If you have any suggestions as to how you'd like to be alerted to a problem with an object, bearing in mind that the alert might also show for legitimately unreadable parts of a script file, please tell us so that we can incorporate your feedback.

  Michelle T January 25, 2008 07:32

  - 0 +
• 
  a pop up or alert window that steals focus is probably too intrusive, given that there are serveral valid situations where this will happen as you point out Michelle
  
  But perhaps a pop up bar like the Interactive Help bar, or some other type of non focus stealing alert/notification could occur if any scripts had problems being read by the parser, and the user could click it to review the problems that occured
  
  It would also be good to include a severity level, eg from WARNING if some parts of the file couldnt be parsed, but some valid table/procedure creation code was found and loaded, versus ERROR if the entire file was ignored as nothing could be made sense of. If possible output from the parser could be shown too, indicating the problem... in the OPs example something like "Invalid SELECT list on line xyz" would immediately pinpoint the problem. A way to view or jump to the section in the script file would be helpful too
  
  That way after running a compare, the user would see the error bar notification and be able to click it for more details if they want, then make the decision if the compare was good or not. In the above case, the ERROR and completely ignored file would be identified, corrected and then recompare the project. In a case where it was some database creation code, the user decides that doesnt bother them and continues with their work.

  rgribble January 31, 2008 00:05

  - 0 +

Add comment

Please sign in to leave a comment.