| Anonymous | Login | Signup for a new account | 2010-07-29 10:17 EDT | ![]() |
| Main | My View | View Issues | Change Log | Roadmap | Wiki | ManTweet | Repositories |
| View Issue Details [ Jump to Notes ] [ Wiki ] | [ Issue History ] [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0007702 | mantisbt | sql | public | 2007-01-04 09:52 | 2009-06-27 09:56 | ||||||
| Reporter | srouleau | ||||||||||
| Assigned To | |||||||||||
| Priority | normal | Severity | major | Reproducibility | always | ||||||
| Status | confirmed | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 1.1.0a2 | ||||||||||
| Target Version | 1.3.x | Fixed in Version | |||||||||
| Summary | 0007702: The 'VERSION' fields should be normalized | ||||||||||
| Description | We currently store VERSION, FIXED IN VERSION and TARGET VERSION denormalized, such that renaming a version will not impact any of the rows using that version. This is wrong, IMHO. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
Notes |
|
|
Blue Ninja (reporter) 2007-01-05 10:01 |
Agreed - I use a version named "Current Development Version" while working on changes, then rename it to the actual version number upon release. It would make sense that renaming it would affect existing references in the changelogs and such. |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2007-01-04 09:52 | srouleau | New Issue | |
| 2007-01-05 10:01 | Blue Ninja | Note Added: 0013899 | |
| 2008-09-08 11:42 | Sergiodf | Issue Monitored: Sergiodf | |
| 2008-09-08 14:09 | brianstv | Issue Monitored: brianstv | |
| 2009-06-27 09:56 | dhx | Status | new => confirmed |
| 2009-06-27 09:56 | dhx | Target Version | => 1.x.x |
| MantisBT 1.2.2 git master-1.2.x[^]
Copyright © 2000 - 2010 MantisBT Group
Time: 0.2080 seconds. memory usage: 1,940 KB |