Yes, LOB values are stored separately in H2 and in many other DBMS, unlike other values.
When you read a row, all non-LOB values are read, presence of some large value may slow down the whole operation even when it doesn't need to read them. Presence of large LOB value is cheap here, because only its descriptor will be read, but not the actual value. On the other hand, when you need to read a LOB value, a separate read operation is required. Small LOB values (up to 256 bytes by default, the documentation is outdated) in H2 are stored directly in a row like all other values. You can set MAX_LENGTH_INPLACE_LOB to a larger value if you wish. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/84092a6c-451a-4bc0-8b82-156ed5908f9bo%40googlegroups.com.
