Hi, I suggest to use just BLOB, without the size.
The value returned in the database meta data is (has to be) incorrect in this case, because the JDBC specification says the column COLUMN_SIZE of DatatabaseMetaData.getColumns is "int". And "int" doesn't support values larger than 2 GB. However, internally, H2 is using "long" so it shouldn't be a problem. Did you actually try to store a large value? It works according to my test case: http://h2database.com/p.html#7f7a13cdfef12ac9c6a0b208c577f97e If this test case or your own test case fails for you: what version of H2 do you use? What is the exception and stack trace you get? What file system do you use? FAT is known to not work, the workaround is to use the split file system, see http://h2database.com/html/advanced.html#file_system > We are using a huge h2 database for storing compressed ISO files. To tell you the truth, I would probably store them externally, as files :-) Unless if you want to create a fulltext index, or if you want to ensure that duplicate files are only stored once (but for that you will need the new feature h2.lobInDatabase). Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" 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/h2-database?hl=en.
