Forum BigDB Bad bug when editing objects manually

Discussion and help relating to the PlayerIO database solution, BigDB.

Bad bug when editing objects manually

Postby cjcenizal » March 31st, 2011, 6:55 pm

Hi guys, the bug I found results in loss of data. Here's the steps to reproduce:

1. Access BigDB and create a table called TestTable.
2. Click New Object. Call its key "Test". Hit Create Object.
3. Add a new Array property called Prop to the Test object. Hit OK, and Save Changes.
4. Populate the Prop Array with at least one element of any type. Save Changes.
5. Refresh the page, or re-access the TestTable so you are seeing it afresh.
6. Click "show array" to see the contents of Prop.
7. Click Prop so you can view options for renaming it and editing its type.
8. Don't change anything, just hit OK and Save Changes.
9. The Prop array has now been emptied of all its elements!

This data appears to be lost. It seems you're overwriting the contents of the property of the object if its type is changed. However, if the user just looks at the options for changing type, but decides against it, this overwrite shouldn't take place, right?
cjcenizal
Paid Member
 
Posts: 115
Joined: March 29th, 2011, 12:31 am

Re: Bad bug when editing objects manually

Postby Henrik » April 1st, 2011, 10:38 am

Thanks for the bug report, we'll look into this!
Henrik
.IO
 
Posts: 1880
Joined: January 4th, 2010, 1:53 pm


Return to BigDB



cron