Export should include images - or make different entire "backup" strategy that includes them

[GoogleCodeExporter]

I was just looking at the export file, and shouldn't the images be part of the 
export (and subsequent import)?  Especially if you've gone to the trouble of 
creating a few images of your own!

Thanks!

Original issue reported on code.google.com by RobGre...@gmail.com on 25 Aug 2010 at 5:29

[GoogleCodeExporter]

When you say the export file, you mean the CSV or the database?  

Really I think we will end up removing the export database option because we 
can't guarantee compatibility when you restore the same way we can when you 
upgrade the version of the app (if we change the db). So eventually that will 
leave the database file out of it. 

That leaves the CVS, I don't think we want to put that amount of data in the 
CSV, but maybe we could make it a separate option (base64 encoded images?). Or 
we could come up with another export type altogether that's a better overall 
"backup" and zips up the images directory along with making a CSV file for the 
data. 

Overall the big idea with images is that they aren't part of the data, and they 
can be re-retrieved with the "reset all images" button and so on (this works 
pretty well even when you have 500 books, in my experience). But, all of that 
breaks down for custom images. If you make your own, you're right, the reset 
won't work. But, your own would still be in the gallery. It would be tedious, 
but you could re-assign those. 

Original comment by charlie....@gmail.com on 29 Aug 2010 at 6:55

• Changed title: Export should include images - or make different entire "backup" strategy that includes them
• Changed state: Accepted

[GoogleCodeExporter]

Original comment by charlie....@gmail.com on 29 Aug 2010 at 6:58

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I've actually been using the .db backup.  Either way (CSV or database), I 
imagine the images should be there... and maybe just the custom-added ones 
since the others could be re-downloaded.

Original comment by RobGre...@gmail.com on 29 Aug 2010 at 7:49

[GoogleCodeExporter]

Just thought of something -- a number of the book covers did NOT match my book. 
 If I remember correctly, there are many covers for a book over time.  If 
you're picky like me, you'd prefer the one that matches your actual book.  So, 
probably exporting and importing every cover is actually important.  Well, to 
me.  :-)

Guess that means I'm arguing that the book cover IS part of the data and needs 
to get backed up too.

Original comment by RobGre...@gmail.com on 30 Aug 2010 at 9:44