Opened 15 years ago
Closed 15 years ago
#1182 closed defect (fixed)
Maestro: expression editor throws MgNullPropertyValueException
Reported by: | jbirch | Owned by: | ksgeograf |
---|---|---|---|
Priority: | low | Milestone: | Maestro-2.0 |
Component: | Maestro | Version: | |
Severity: | trivial | Keywords: | |
Cc: | External ID: |
Description (last modified by )
When trying to enumerate values in a particular property in the expression editor, an MgNullPropertyValueException is thrown if any null values exist for that property.
This makes it difficult to work with that that contains these values; the current workaround I'm using is FDO Toolbox, but this can be difficult when the data isn't local.
It would be great if Maestro's implementation of the expression editor could be modified to suppress these exceptions or, preferably, insert NULL as one of the choices in the value picker.
Change History (4)
comment:1 by , 15 years ago
Description: | modified (diff) |
---|
comment:2 by , 15 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:3 by , 15 years ago
Milestone: | → Maestro-2.0 |
---|---|
Resolution: | invalid |
Status: | closed → reopened |
Oops, I have actually added a fix for this, but there is a bug in the fix. Basically, if there is an MgNullValue exception, the query is retried with a "where [value] != NULL".
The problem is that it is MapGuide that throws these exceptions, so there is no return data. This was fixed for some providers in the http handler, where it would previously just attempt to read values, without checking if they are null.
Related issues are issue #1080 and issue #456.
I'm closing as invalid, because Maestro cannot do anything about the error in MapGuide.