Enhanced error reporting on DataConnection save
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.
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.
Change History
(6)
| Description: |
modified (diff)
|
| Description: |
modified (diff)
|
| Summary: |
Connecting to SQL Server can throw errors → Enhanced error reporting on DataConnection save
|
| Description: |
modified (diff)
|
| Milestone: |
→ Maestro-2.1.x
|
| Resolution: |
→ fixed
|
| Status: |
new → closed
|
| Milestone: |
Maestro-2.1.x → Maestro-3.0
|
Yeah I'm noticing this on one of my current client's data sets. This doesn't just apply to SQL Server.