A very many platforms, applications and filesystems have trouble with files that exceed 2GB. Even if Android's dalvik/Java-like libraries are okay with it, the sqlite implementation may not be. Even if sqlite can deal with huge files, the SD card filesystem is surely FAT32, which will limit you to 4 GB again.
Break up your data. I have no idea what (x, y, z, s) are, but it comes to mind that it's some sort of voxel implementation, maybe like the game Minecraft on personal computers. Minecraft implements their game world in "chunks" with a limited range of x, y, z coordinates, and only stores the BYTE s data for each chunk in separate files. They can achieve billions of s data records in this way, without going over a few megabytes per file. Even if you're not working with this sort of data, it does seem really silly to expect sqlite to perform as well with an all-integer-addressable data set, as some specialized file format. On Jan 14, 11:39 am, Marcin Orlowski <[email protected]> wrote: > On 14 January 2011 17:38, Marcin Orlowski <[email protected]> wrote: > > > On 14 January 2011 16:58, Menion <[email protected]> wrote: > >> only one info > > >> database 1.8GB works fine > >> database 2.5GB do not work! > > > Is your DB stored on SD card or in internal memory? > > Or could it be you hit something DB internally got old signed int vs > unsigned int issue? -- 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
