Not logged in
  1. Add support for a SHARD KEY in the table definition. This is passed down into the storage engine as a hint. The storage engine is free to ignore the hint.

  2. Forward port all query optimizer enhancements implemented in SQLite3 over the previous year into SQLite4.

  3. Review all other changes made to SQLite over the previous year and forward port all that seem appropriate.

  4. Use decimal arithmetic everywhere within the code. Avoid the use of IEEE 754 binary floating point, except for APIs that have "double" parameters or return values.

  5. Carefully review the entire API and look for other ways to make it simpler and more robust.

  6. Change memory allocation routines to be methods of sqlite4_mm instead of methods of sqlite4_env.

    1. sqlite4_mprintf()
    2. sqlite4_vmprintf()
    3. sqlite4_malloc()
    4. sqlite4_free()
    5. sqlite4_realloc()
  7. Add a new extended error code for every error where doing so makes any sense at all.