As soon as I hit Send, I thought of something. This only holds until
you actually read the destination database. So in my example code,
after the check that the database contains the right data
("e\nf\ng\nh" bit), another page_size check will show 4096 instead of
1024. So the window for this to confuse something is pretty narrow.
-scott
On Thu, Oct 27, 2016 at 4:08 PM, Scott Hess <sh...@google.com> wrote:
> Here's an example code for reference:
> http://pastebin.com/pQdfkneR
>
> I just noticed that if you use sqlite3_backup() where the source
> database page_size isn't the same as the destination database
> page_size, after a successful backup the destination database
> continues to report the page_size from before the backup was made. In
> most cases, this is not the case. For instance, if you try to change
> the page_size on a database which contains pages, then later query the
> page_size, you will get back the _actual_ page_size, not the one you
> set.
>
> Is this intentional?
>
> -scott
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
