rgw/sfs: change db schema as described in ADR.

[0xavi0]

Changes the db schema following this ADR.

It deletes repeated fields that we had in objects vs versioned_objects tables and creates new fields in the versioned_objects table.

Logic of sfs was intentionally not updated in this PR. (For example new field version_type is added to the schema, but still not used).
Updates in logic, specially in versioning logic, will come in a future PR.

New Features:

Sqliteorm type bindings for the following types.

• uuid_d
• ceph::real_time
• rgw::sal::sfs::ObjetState
• rgw::sal::sfs::VersionType

In general, any enum type that has a LAST_VALUE item assigned to the last valid value and that also starts with 0 is eligible to be binded to sqliteorm, as the type binding for enums is generic.

For example: you can create an enum like:

enum class TestEnum  {
  WHATEVER = 0,
  SOMETHING_ELSE,
  AND_THIS,
  LAST_VALUE = AND_THIS
};

and use it right away in sqliteorm.

Custom type bindings code are using exceptions because they are specialisations of sqlite_orm.

Object has no explicit conversion code

As all the types in the object table are compatible with sqliteorm we don't need extra conversion layer.
This is a preview of what we can do with the rest of database objects once BLOBS are also type bound in the future.
That was not done in this PR to avoid too many changes.

Note: The new type VersionType was added as a new file version_type.h because we are in a re-design process and I wasn't sure if it should be located in any other existing file that might be eligible to be deleted in the near future.

Fixes: https://github.com/aquarist-labs/s3gw/issues/480

Signed-off-by: Xavi Garcia xavi.garcia@suse.com

Checklist

• Tracker (select at least one)
  • References tracker ticket
  • Very recent bug; references commit where it was introduced
  • New feature (ticket optional)
  • Doc update (no ticket needed)
  • Code cleanup (no ticket needed)
• Documentation (select at least one)
  • Updates relevant documentation
  • No doc update is appropriate
• Tests (select at least one)
  • Includes unit test(s)
  • Includes integration test(s)
  • Includes bug reproducer
  • No tests

[irq0]

good stuff!

❤️ the type binding change