Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DatabasePlatformTested bySuccess RC1?Notes
MySQL osx

(tick)

(tick)

Danny Bernstein: (error)Restoring v1 after creating v2 does not seem to work:

Steps to reproduce: 1. Create a binary with fileA.jpg

2. Create version v1.

3. Update binary with fileB.jpg

4. Create version v2.

5. Click on versions link and click on v1 link.

6. Click "Revert to this Version"

7. Return to binary resource metadata page. Notice the file associated with the version fileB.jpg rather than the expected fileA.jpg. It does not appear that the version was reverted.

Joshua Westgard: Hey Danny Bernstein, when I tested the versioning I was just making changes to metadata not binaries and didn't notice any problems; after seeing your note, however, I tried with a binary and did notice that the browser cached the previous version, so after restoring it was still displaying the previous data, but upon refreshing the resource page the restored version was visible as expected. Any chance this is the same problem you were seeing?

Joshua Westgard: could be, though I thought I did a hard refresh. I'll try it again to conf hirm.

Joshua Westgard: I must not have done a hard refresh. So yes after a hard refresh it worked. I wonder if it should be a logged as a bug nevertheless. Ideally any refresh would not be required at all much. A Command-R refresh doesn't refresh the page. Only Command-Shift-R. It seems like it could be a source of confusion. Perhaps a JIRA is warranted.


PostgreSQLosxJoshua Westgardconfig successful; testing in progress
PostgreSQL linux


...