Re: [h2] What is the best way to store large text values?
If you're shutting the DB down normally, it should start up pretty quickly. H2 is unfortunately not great with TEXT/LOB data. At that size you could try storing it in a VARCHAR column. You'll have to be more specific about what exactly is slow. -- 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 h2-database+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/1e028e43-903d-a322-2c42-27fa63d6393a%40gmail.com.
[h2] What is the best way to store large text values?
I have a table which contains large JSON text, each row is about 100 KB. So entire database file may grow up to 15 GB, which makes it very slow, it even takes forever to open the database. Despite the fact that c_data is a CLOB column. create table t_data ( idinteger auto_increment not null, c_some_column_1 integer, c_some_column_2 integer, c_datatext, constraint pk_t_data primary key (id) ); Am I doing something wrong? Should I store the data in separate text files to keep DB as lightweight and quick as possible? Are there better solutions? I use H2 database 1.4.197. -- 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 h2-database+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/87885d29-98f8-4dcd-bb59-e509223473b2%40googlegroups.com.
[h2] What is the best way to store large text values?
I have a table which contains large JSON text, each row is about 100 KB. So entire database file may grow up to 15 GB, which makes it very slow, it even takes forever to open the database. Despite the fact that c_data is a CLOB column. create table t_data ( idinteger auto_increment not null, c_some_column_1 integer, c_some_column_2 integer, c_datatext, constraint pk_t_data primary key (id) ); Am I doing something wrong? Should I store the data in separate text files to keep DB as lightweight and quick as possible? Are there better solutions? I use H2 database 1.4.197. -- 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 h2-database+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/20177cba-96df-4cec-bbb0-6c938a7b08fa%40googlegroups.com.
