699622 - Unpack extensions.sqlite from omni.jar when profile is created

Status: RESOLVED WONTFIX

(Toolkit :: Add-ons Manager, defect)

Description

[Vladan Djeric (:vladan)]

Attachment: Code for unpacking the DB when profile is created

To improve first run performance, we will be unpacking pre-created SQLite databases from omni.jar on profile initialization (see bug 691268).

This change extracts formhistory.sqlite from omni.jar when the database doesn't exist. The extracted DB contains the DB schema but no rows. If extraction fails for whatever reason, an error is logged and the DB is created from scratch as before.

Comment 1

[Dave Townsend [:mossop]]

For mobile we don't create extensions.sqlite on startup so this will degrade Ts there

Comment 2

[Vladan Djeric (:vladan)]

(In reply to Dave Townsend (:Mossop) from comment #1)
> For mobile we don't create extensions.sqlite on startup so this will degrade
> Ts there

But then XPIDatabase.openConnection() would never be called on mobile so we would never extract the DB from omni.jar. It's on the same path as DB creation.

Comment 3

[Dave Townsend [:mossop]]

Comment on attachment 571816 [details] [diff] [review]
Code for unpacking the DB when profile is created

With all the changes lately we'll need a new patch here. I'd really like to see a conclusion in bug 699615 first though.

Comment 4

[:Gavin Sharp [email: [e-mail]]]

this db doesn't exist anymore