Community
Participate
Working Groups
Currently, when a specific 4.0 IStore implementation is used with data that was written by an earlier version of the same implementation, it will fail in an unpredictable way. Ideally, a 4.0 implementation would recognize 3.0 or 2.0 data as such, and either gracefully reject it, or, if possible, patch the data to become 4.0-compliant.
After backporting the export feature from 4.0 to 2.0 (see bug 333260), this has become low priority, possibly even irrelevant.
(In reply to comment #1) > After backporting the export feature from 4.0 to 2.0 > (see bug 333260), this has become low priority, possibly > even irrelevant. You're right Caspar, it's pretty irrelevant now. Resolving as WONTFIX.
Changed my mind. Resolving as WORKSFORME.
Moving all open enhancement requests to 4.1
Closing.