Mitchell Vincent wrote:
So is a 60%ish reduction in DB size from 2.8.16 to 3.3.13 normal?
Don't know about "normal" but ISTR version 3 did bring some fairly major
improvements in file size. Given that you have your data in both SQLite
formats would it not be fairly easy to dump both
On 3/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> So is a 60%ish reduction in DB size from 2.8.16 to 3.3.13 normal?
>
3.3.13 typically generates database files that are 30-40% smaller
than 2.8.16. 60% seems excessive, but is not outside the range of
possibility. What kind of data
"Mitchell Vincent" <[EMAIL PROTECTED]> wrote:
> I'm converting a bunch of databases from SQLite 2.8.16 to SQLite
> 3.3.13 and am seeing something pretty amazing space saving. So good
> that it might be too good to be true!
>
> For example, a 17 meg database is cut down to 7 megs. That's fantastic
On 3/12/07, Mitchell Vincent <[EMAIL PROTECTED]> wrote:
I'm converting a bunch of databases from SQLite 2.8.16 to SQLite
3.3.13 and am seeing something pretty amazing space saving. So good
that it might be too good to be true!
For example, a 17 meg database is cut down to 7 megs. That's
I'm converting a bunch of databases from SQLite 2.8.16 to SQLite
3.3.13 and am seeing something pretty amazing space saving. So good
that it might be too good to be true!
For example, a 17 meg database is cut down to 7 megs. That's fantastic
if it's just that SQlite is *that* much better at
5 matches
Mail list logo
