Reset SQL migrations

[mrferris]

Creates all tables with their needed columns, rather than adding columns later on. Will require a DB wipe.

[pipermerriam]

so sorry if you already had plans to add these.

[pipermerriam]

We need two indexes here:

• an index on (record_id, key) unique index. which enforces the constraint and allows quick querying of all the keys for a given record_id.
• an index on only key so that we can lookup all the records with a given key.

[mrferris]

so sorry if you already had plans to add these.

Hadn't thought about most of these indices/queries, so thanks!

Currently seeing sea orm generating invalid sql syntax when creating non-unique indices (which is why they're commented out here):

CREATE TABLE "content" (
      "id" serial NOT NULL PRIMARY KEY,
      "protocol_id" integer NOT NULL,
      "content_key" bytea NOT NULL,
      "content_id" bytea NOT NULL,
      "first_available_at" timestamp with time zone NOT NULL,
      CONSTRAINT "idx-unique-id-protocol-and-key" UNIQUE ("protocol_id", "content_key", "content_id"),
      CONSTRAINT "idx-unique-protocol-and-key" UNIQUE ("protocol_id", "content_key"),
      CONSTRAINT "idx-unique-protocol-and-id" UNIQUE ("protocol_id", "content_id"),
      CONSTRAINT "idx-available-and-protocol" ("first_available_at", "protocol_id")
    )

Error: Execution Error: error returned from database: syntax error at or near "("

[pipermerriam]

I think I ran into this same issue, any chanced you looked upstream to see if this is a known sea-orm issue?

Lets move forward at least with the unique ones and open an issue to figure out the non-unique ones at a later date.