Opened 15 years ago
Last modified 14 years ago
#1401 closed enhancement
Enhanced error reporting on DataConnection save — at Version 2
| Reported by: | jbirch | Owned by: | jng |
|---|---|---|---|
| Priority: | low | Milestone: | Maestro-3.0 |
| Component: | Maestro | Version: | 2.1.0 |
| Severity: | minor | Keywords: | |
| Cc: | External ID: |
Description (last modified by )
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 (2)
comment:1 by , 15 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 15 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | Connecting to SQL Server can throw errors → Enhanced error reporting on DataConnection save |
Note:
See TracTickets
for help on using tickets.
