[Default] On Thu, 8 Nov 2007 00:50:47 +0300, "Igor Sereda"
<[EMAIL PROTECTED]> wrote:
>Thank you! How about separate DB just for large texts?
>Would that be an overkill?
I think it would be overkill indeed. I also think it's better to
have 'too large' pages for the 'numeric table' than to have
"Igor Sereda" <[EMAIL PROTECTED]> wrote:
> Thank you! How about separate DB just for large texts? Would that be an
> overkill? We could use different page sizes for the two DBs. I'm not sure
> how well transactions over several DBs are handled though.
>
You could do that, but the benefits are
PROTECTED]
Sent: Thursday, November 08, 2007 12:30 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Optimizing performance by moving large texts into a
separate table
"Igor Sereda" <[EMAIL PROTECTED]> wrote:
> We have a database that can possibly grow into millions of rows. So
[EMAIL PROTECTED] wrote:
"Igor Sereda" <[EMAIL PROTECTED]> wrote:
We have a database that can possibly grow into millions of rows. Some =
tables have TEXT fields, which may store texts of signigicant length. =
All other data is mostly numeric values.
We have a thought of moving all large
"Igor Sereda" <[EMAIL PROTECTED]> wrote:
> We have a database that can possibly grow into millions of rows. Some =
> tables have TEXT fields, which may store texts of signigicant length. =
> All other data is mostly numeric values.
>
> We have a thought of moving all large texts into a separate
We have a database that can possibly grow into millions of rows. Some tables
have TEXT fields, which may store texts of signigicant length. All other data
is mostly numeric values.
We have a thought of moving all large texts into a separate table, and
replacing text_column with text_id in the
6 matches
Mail list logo
