Changes between Version 1 and Version 2 of Ticket #1401


Ignore:
Timestamp:
Jul 11, 2010, 10:00:17 PM (14 years ago)
Author:
jbirch
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1401

    • Property Summary Connecting to SQL Server can throw errors → Enhanced error reporting on DataConnection save

  • Ticket #1401 – Description

    v1 v2  
    1 It would be useful if, when getting an !MgClassNotFoundException in reply to a !GetIdentityProperties call when saving a !DataConnection, Maestro could inform the user that it could not determine the identity property for X class, rather than just dumping the exception to the screen.  A smart user should then be able to figure out from this that the error is occurring because of a missing PK.
     1When saving a SQL Server DataConnection, if one or more of the tables does not have a primary key set, Maestro presents a screen to the user with the text of an MgClassNotFoundException.  This isn't especially easy to figure out for end users.
     2
     3It would be useful if, when this occurs, Maestro could inform the user that it could not determine the identity property for X class.  A smart user should then be able to figure out from this that the error is occurring because of a missing PK.