Re: [sqlite] How to "upgrade" a DB without write access to its file, or to the direction it's in?

Another option: Copy the meta-data to an in-memory-DB. As you "load all meta data into memory" anyway this seems a viable option. ATTACH ':memory:' AS mem INSERT INTO mem.Table SELECT * FROM Table (repeat for each table, you may want to create/recreate constraint and indices in the

Re: [sqlite] How to "upgrade" a DB without write access to its file, or to the direction it's in?

On Wed, Aug 7, 2013 at 6:36 PM, Richard Hipp wrote: > On Wed, Aug 7, 2013 at 12:15 PM, Dominique Devienne >wrote: > > > On Wed, Aug 7, 2013 at 2:45 PM, Clemens Ladisch > > wrote: > > > > > Dominique Devienne wrote: > > > > We can of

Re: [sqlite] How to "upgrade" a DB without write access to its file, or to the direction it's in?

On Wed, Aug 7, 2013 at 12:15 PM, Dominique Devienne wrote: > On Wed, Aug 7, 2013 at 2:45 PM, Clemens Ladisch > wrote: > > > Dominique Devienne wrote: > > > We can of course copy the db file somewhere else with r/w access, or > copy > > > the DB into an

Re: [sqlite] How to "upgrade" a DB without write access to its file, or to the direction it's in?

On Wed, Aug 7, 2013 at 2:45 PM, Clemens Ladisch wrote: > Dominique Devienne wrote: > > We can of course copy the db file somewhere else with r/w access, or copy > > the DB into an in-memory DB (for each table, create table memdb.foo as > > select * from dskdb.foo) and upgrade

Re: [sqlite] How to "upgrade" a DB without write access to its file, or to the direction it's in?

Dominique Devienne wrote: > We can of course copy the db file somewhere else with r/w access, or copy > the DB into an in-memory DB (for each table, create table memdb.foo as > select * from dskdb.foo) and upgrade and read that one instead, but I was > wondering whether there's another better

[sqlite] How to "upgrade" a DB without write access to its file, or to the direction it's in?

We use SQLite for persistence of our project meta-data (the data itself is still in a proprietary binary format). For now, on project load, the meta-data DB file is read in full into memory (C++ objects) then closed, and re-written from scratch on save or save-as, instead of trying to update it in

Re: [sqlite] How to upgrade from SQLite 3.7.4 to 3.7.6.3

vin <slav...@bigfraud.org> > Subject: Re: [sqlite] How to upgrade from SQLite 3.7.4 to 3.7.6.3 > To: "General Discussion of SQLite Database" <sqlite-users@sqlite.org> > Date: Wednesday, May 25, 2011, 5:33 PM > > On 25 May 2011, at 10:11pm, Long, Matthew wrote: > >

Re: [sqlite] How to upgrade from SQLite 3.7.4 to 3.7.6.3

On 25 May 2011, at 10:11pm, Long, Matthew wrote: > I have firefox Sqlite manager installed, and I see the Sqlite version: > 3.7.4 installed when I start Sqlite manager. How do I upgrade 3.7.4 to > 3.7.6.3? You can't upgrade, you have to wait for programmers to do it. It is probably using

[sqlite] How to upgrade from SQLite 3.7.4 to 3.7.6.3

Hi All, I have firefox Sqlite manager installed, and I see the Sqlite version: 3.7.4 installed when I start Sqlite manager. How do I upgrade 3.7.4 to 3.7.6.3? When visit the sqlite dowload page, I'm not sure what to install since I installed using a add-on for firefox.

Re: [sqlite] How to Upgrade

Vishal Kashyap wrote: Dear All , I was wondering to upgrade from one SQLite version to other (refering 3.x). Should I just replace the old sqlite3.exe file with the new one and use the database as it is. The database I have created dabase in 3.2.7 and want to move to 3.3.4. How to go about

[sqlite] How to Upgrade

Dear All , I was wondering to upgrade from one SQLite version to other (refering 3.x). Should I just replace the old sqlite3.exe file with the new one and use the database as it is. The database I have created dabase in 3.2.7 and want to move to 3.3.4. How to go about it. -- With Best Regards,