You could also try this. I imagine it has to do much less internal querying
to get the job done. This does assume you have a single column PK, beyond
the rowid, that would not change when the other columns changes.
INSERT OR REPLACE INTO T1 SELECT * FROM T2;
DELETE FROM T1 WHERE pk NOT IN
dang it. changes.html, explain query plan. sorry.
On 2/24/06, deminix <[EMAIL PROTECTED]> wrote:
>
> am I crazy or was there an experimental explain output mechanism, that
> attemped to output the plan in something closer to english. if there was, i
> am unable to f
am I crazy or was there an experimental explain output mechanism, that
attemped to output the plan in something closer to english. if there was, i
am unable to find it on the site documentation anymore. was it removed?
did I imagine the whole thing late some night? :)
--paul
This is definitely the fastest way, if it succeeds. If its performed via
SQLite DDL then it does the appropriate locking on the file etc and returns
nice error codes.
By doing it via the file system (at least on linux), other readers of the
file will continue to read from it... I don't know if
Thank you.
On 1/25/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> deminix <[EMAIL PROTECTED]> wrote:
> > I was curious if a single page of the database was limited to at most
> one
> > record, aka can records be packed into a single page?
>
> Mul
5 matches
Mail list logo