[PGSQL] Implement PostgresCustomIdentityDAO

[quantranhong1999]

Why

We need a CustomIdentityDAO backed by Postgres (for Identity/get + set usage).

How

• Table structure:

  CREATE TABLE custom_identity (
  username TEXT,
  id UUID,
  name TEXT,
  email TEXT,
  reply_to TEXT[],
  bcc TEXT[],
  text_signature TEXT,
  html_signature TEXT,
  sort_order INT,
  may_delete BOOLEAN,
  PRIMARY KEY (username, id)
  );

  An additional index on username would help list all identities for a given user quickly.

• Implement PostgresCustomIdentityDAO

• Guice binding in PostgresJMAPModule.

DoD

Pass contract test CustomIdentityDAOContract.

[chibenwa]

Listing all signature of a given user shall be quick.

Otherwise OK to me.

[Arsnael]

Listing all signature of a given user shall be quick.

why? There is no api that fetches only signatures for theuser, we always return the full identity object. Or is it something new? A query fetching just signatures of a user? But I think the front just get directly the all Identity so we are confused here, as we don't do that with Cassandra too.

[chibenwa]

I mean listing all identities for a given user shall be quick.

[quantranhong1999]

I mean listing all identities for a given user shall be quick.

This should be solved with an additional index on username.

[hungphan227]

CassandraCustomIdentity use UDT array for reply_to and bbc. Postgresl support UDT but jooq does not support it well. Therefore, I intend to use 2 dimension array (TEXT[][]) for reply_to and bbc

[vttranlina]

CassandraCustomIdentity use UDT array for reply_to and bbc. Postgresl support UDT but jooq does not support it well. Therefore, I intend to use 2 dimension array (TEXT[][]) for reply_to and bbc

or JSON for simple

[hungphan227]

pr https://github.com/apache/james-project/pull/1960