| 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. |
| | 1 | When 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 | |
| | 3 | It 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. |
