SQLite Forum

Impact analysis for "larger-databases" change

Impact analysis for "larger-databases" change

(1) By Kevin Youren (KevinYouren) on 2021-04-08 01:37:52 [source]

My apologies if this type of question has been asked before, or if it should be asked in the Fossil forum.

If possible, could you tell about the following change in July last year.

"Allow for page numbers as large as 4294967294 (0xfffffffe) which means database files as large as 281 TB. (check-in: 166e82dd user: drh tags: trunk)"

How did you know which programs and which lines needed changing?

(2) By ThanksRyan on 2021-04-08 04:05:23 in reply to 1 [link] [source]

Here's the commit for that change. You can get a head start on reading the code:


Here's a forum comment on the enhancement:


(3) By Kevin Youren (KevinYouren) on 2021-04-08 04:40:13 in reply to 2 [link] [source]

Thanks for the forum entry.

I found the list of programs already.

What I am asking is: 
 "How is the list of programs that require change(s) produced?"

(4) By anonymous on 2021-04-08 23:50:46 in reply to 3 [link] [source]

By having someone who is familiar with the code read through it and look for instances of a signed integer variable being used to store a page number?