PRAGMA page_size has no effect, and SQLITE_DEFAULT_PAGE_SIZE 512 has no effect.

[trianglesis]

Hello,
As described at this issue post: siara-cc/esp32_arduino_sqlite3_lib#92 (comment)

I'm trying to reduce SQLite's memory footprint by lowering the page size, but this command or definition has no effect.

Hello,

Can you please point me in the right direction? I'm having issues with setting page_size:

I'm using two approaches, neither of which is working. As soon as the database is created, and I'm checking it in DB Browser (downloaded from ESP32 via file server to my PC), it shows page_size 4096

1. Set `#define SQLITE_DEFAULT_PAGE_SIZE 512` at the header of my SQL driver file, where I include `#include "sqlite3.h"` and `#include "sqllib.h"`, later I can see `#define SQLITE_DEFAULT_PAGE_SIZE 512` in `managed_components\nopnop2002__sqlite3\config_ext.h` file, which is fine.

2. Set the query: `PRAGMA page_size=512; VACUUM;` as soon as the newly created DB is opened, before any table creation.
   Literally: `rc = db_query(xMessageBufferQuery, db, "PRAGMA page_size=512; VACUUM;");`

I was trying actually delete the file via file browser and programmatically with unlink(db_name); - right before init.

And no effect.

PRAGMA main.page_size = 1024;
PRAGMA main.page_size;

The author of the original lib says he changed page_size some time ago: siara-cc/esp32_arduino_sqlite3_lib#92 (comment)

[nopnop2002]

The author of the original lib says he changed page_size some time ago: siara-cc/esp32_arduino_sqlite3_lib#92 (comment)

This is for the Arduino environment, not the ESP-IDF environment.

This repository is for the ESP-IDF environment.

Your PR to fix this issue is welcome.

[trianglesis]

You mentioned your fork is only optimised for the building procedure for IDF.

Although it is a very nice library, it cannot be built with ESP-IDF Ver5.
Therefore, We changed it so that it can also be used with ESP-IDF Ver5.

It now looks like the library is poorly ported to IDF.
Please add a note to the README file stating that this fork has many limitations and non-working features.

[nopnop2002]

The original is here.

We believe this fork functions exactly the same as the original.
The defects present in the original are also present in this fork.

Please check if this issue exists in the original.

[trianglesis]

The original is here.

If the original has been fixed, we will correct it here too.

The original is not broken; the fork is.

This has no effect: https://github.com/nopnop2002/esp32-idf-sqlite3/blame/a27228d70b9bcf92149a28e7ea490661f9a9ca4d/components/esp32-idf-sqlite3/config_ext.h#L23

The original: siara-cc/esp32_arduino_sqlite3_lib#92 (comment)

[nopnop2002]

siara-cc/esp32_arduino_sqlite3_lib#92 (comment)

This is NOT original.

The original of this fork is here.

[trianglesis]

Here is the original maintainer siara-cc explaining the SQLITE_DEFAULT_PAGE_SIZE directive: siara-cc/esp32_arduino_sqlite3_lib#92 (comment)

Please read carefully.

This directive SQLITE_DEFAULT_PAGE_SIZE has no effect in your fork.
Please update the README file, adding the features that do not work.

[nopnop2002]

The original version of this fork can be found here.
https://github.com/siara-cc/esp32-idf-sqlite3

No code has been changed from the original.

I only added an example and changed Make to Cmake.

This directive SQLITE_DEFAULT_PAGE_SIZE has no effect in your fork.

This directive SQLITE_DEFAULT_PAGE_SIZE has no effect in ORIGINAL.

[trianglesis]

The original version of this fork can be found here. https://github.com/siara-cc/esp32-idf-sqlite3

No code has been changed from the original.

I only added an example and changed Make to Cmake.

This directive SQLITE_DEFAULT_PAGE_SIZE has no effect in your fork.

This directive SQLITE_DEFAULT_PAGE_SIZE has no effect in ORIGINAL.

So, updating the README file will help people understand the library's supported level.
It can save a few days in troubleshooting.

[nopnop2002]

I added this to README.

If there is a issues in the original, the same issues will be found in this repository.
If you find any issues, we welcome your PR to resolve them.