| Author: | Paul Balm [pbalm@esa.int] |
| Date: | 04-12-2006 |
| Summary: | Proposal status and various SPR's. |
|
SPR 771 | The proposal loader was capable of writing NULL into a table (SOURCE), after which no tool would ever be able to read back data from this table. This has been identified as a JDBC driver problem. Upgrading to the latest version solved the problem. |
|
SPR 794 | The design of the PATTERN_POINTS table, storing the pointings of custom pointing patterns, has been modified. This pointings are stored in this table along with an index indicating their position in the list of pointings. In the new design it is no longer possible to get two pointings with the same index. |
|
SPR 806 | The system-generated e-mails are automatically signed with the real-world name of the user currently logged on. The user was identified by his ID, but it turns out that this ID can change if a new database dump is imported. The user is now keyed by his username, which is the same on all systems (operation database, test database, etc.). |
 |
SCR 582 | The proposal status can always be directly derived from the observation statuses. From this release on, it is therefore no longer a field that is editable by the user. Instead, the database will make sure it is inline with the observation statuses. |