Hi, > I saw an old post about the poor state of XA support in H2.
The javax.transaction.xa and javax.sql interfaces are still not fully supported. Partially this is because I don't understand how the API is supposed to work exactly. If there is a problem with the behavior, patches are always welcome (specially test cases). > All of them (I believe H2 included) loaded the entire > BLOB into memory For H2, this is no longer the case (actually since quite a long time). The last time I checked, it was a problem for MySQL. > Another reason I think it might make sense to store files outside of > the database is that I believe it reduces the probability of losing > data. It depends where else you store the file. If simply on the file system, then the probability to lose data is higher, because there is no transaction log for the LOB. H2 first stores the large object in the transaction log (WAL), and only then in the data area (like all other changes). This is slower than what other databases do, but it ensures all LOB operations are transactional. 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.
