feat: postgres schema #395
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I've taken the schema from #263 with the following changes: * Primary keys are called `id` except where we're using domain data as the primary key (currently only `cid` in content) * Use shortened primary key definition to use `BIGSERIAL` for enhanced readability * Added `nftstorage` schema * Renamed `account` -> `user` * Make `issuer` NOT the primary key on `user`, added `id` column for primary and referenced it from other tables * Prefixed foreign keys with (complete) referenced table name where appropriate * Renamed `cid` in the `upload` table to `source_cid` so more obvious it is the given/original/provided/source CID * Added the `deleted_at` column to `upload` (and had to remove the `UNIQUE` constraint because of it) * Consistent enums capitalization to match web3.storage and niftysave * Added `upload_type` enum * Renamed `content.size` to `content.dag_size` for consistency with web3.storage
Deploying with
|
| Latest commit: |
9c6949c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d2be8717.nft-storage.pages.dev |
hugomrdias
suggested changes
Sep 6, 2021
packages/db/tables.sql
Outdated
| meta jsonb, | ||
| inserted_at timestamp with time zone DEFAULT timezone('utc'::text, now()) NOT NULL, | ||
| updated_at timestamp with time zone DEFAULT timezone('utc'::text, now()) NOT NULL, | ||
| deleted_at timestamp with time zone DEFAULT timezone('utc'::text, now()) |
There was a problem hiding this comment.
adding the deleted_at forces changes in the function.sql, the upload_fn needs to account for this in the ON CONFLICT clause.
i have this task in my todo already
hugomrdias
suggested changes
Sep 6, 2021
3 tasks
|
Generated diagram from here https://dbdiagram.io/d/6137ad47825b5b0146f766cf |
This was referenced Sep 7, 2021
Gozala
reviewed
Sep 14, 2021
|
Closing this as the changes have been manually merged into #263 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've taken the schema from #263 with the following changes:
idexcept where we're using domain data as the primary key (currently onlycidin content).BIGSERIALfor enhanced readability.Addednft_storageschema.account->user.issuerNOT the primary key onuser, addedidcolumn for primary and referenced it from other tables.user.issuertouser.magic_link_idanduser.subtouser.github_id.cidin theuploadtable tosource_cidso more obvious it is the given/original/provided/source CID.deleted_atcolumn toupload(and had to remove theUNIQUEconstraint because of it).upload_typeenum.mime_typetext field toupload.content.sizetocontent.dag_sizefor consistency with web3.storage.