This is Issue 900 moved from a Google Code project.
Added by 2012-06-15T18:45:57.000Z by ndari...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Original labels: Type-Defect, Priority-Medium, Release
<b>OrientDB release? (If you're using a SNAPSHOT please attach also the build</b>
number found in "build.number" file): 12092
<b>What steps will reproduce the problem?</b>
1. Import the attached database dump.
2. After connecting to the database, run "select changes.size() from Script"
<b>If you're using custom settings please provide them below (to dump all the</b>
<b>settings run the application using the JVM argument</b>
<b>What is the expected output? What do you see instead?</b>
I would expect to see a bunch of 1s and a 2, but instead I see all 0s.
<b>If you're describing a performance or memory problem the profiler dump can</b>
<b>be very useful (to dump it run the application using the JVM arguments</b>
<b>Please use labels and text to provide additional information.</b>
OrientDB seems to fail to import this dump, which includes embedded lists of empty strings. It could be that my export is broken too, but I don't know how to easily package a binary database for investigation. Either way, this bug blocks my ability to move an app to production since I can't easily just copy a binary database to my production server.
This is pretty old. Closing it.