Hi, Hm, interesting, Oracle does it the "easy way" then... I didn't know that. That was similar to the original H2 behavior, and them somebody told me this is wrong (I think it was somebody from the Hibernate team, but I don't remember).
I don't have MySQL installed right now, could anybody test it? If not, I will install the latest version and test later on. Regards, Thomas On Thursday, March 26, 2015, Noel Grandin <[email protected]> wrote: > > > On 2015-03-26 08:48 AM, Thomas Mueller wrote: > >> >> >> I didn't know that. I made some tests (see below), and at least Apache >> Derby seems to do that. I'm not sure about other >> > > In Oracle, you may only read a BLOB column in the same order as the SELECT > statement, and the BLOB ceases to be valid as soon as you read the next > column: > http://docs.oracle.com/cd/B28359_01/java.111/b31224/ > jstreams.htm#BHCDJAGI > > Despite a lot of searching, I could not find any information on how this > works in Sybase or MS-SQL-Server. > > -- > You received this message because you are subscribed to the Google Groups > "H2 Database" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
