I agree with Kaiser. Better to store those files outside, in the SDCard for example, and save only file path and metadata in the DB.
I have done things like that on them past with PostgreSQL and MySQL and I do not found a real advantage and several complications. You can use binary columns (BLOB) to store files there. I do not know if SQLite supports something similar, but you can always encode binary data in Base64 or so... Anyeay, I would not do it If I were you. Also bear in mind that SQLite stores a whole database in a single file, so I am pretty sure that you will have real problems with that approach using big media files sooner than later. El 11/07/2012 12:25, "Anton Kaiser" <[email protected]> escribió: > Don't do that. There is really no need to bloat databases with files. Save > the file on the file system and create an entry for it with the needed meta > data and the file path. > I know that is not what you wanted to hear, but I'm sure you can't give me > a good reason to do it your way ;) > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
