migrate data from entry/bundlers? #3

New issue

Closed

opened 2024-03-10 00:25:57 +00:00 by ewof · 1 comment

ewof commented

2024-03-10 00:25:57 +00:00

is this possible and if so how

hkau commented

2024-03-10 02:46:47 +00:00

Owner

Technically it's possible, the schema is essentially the same with the only difference really being column names and 1 or 2 extras.

Depending on the number of pastes you're migrating this could be pretty easy or pretty hard.

Pastes would have to be re-rendered and have that value filled into the content_html column (from new schema), and GroupSubmitPassword would have to just be dropped entirely.

Metadata would also likely have to be dropped as many of the fields are different now.

Honestly you could likely just import all data and run the following SQL commands (untested, so you should probably review them):

ALTER TABLE "Pastes" CHANGE "CustomURL" "custom_url" VARCHAR(1000000);
ALTER TABLE "Pastes" CHANGE "GroupName" "group_name" VARCHAR(1000000);
ALTER TABLE "Pastes" CHANGE "PubDate" "pub_date" VARCHAR(1000000);
ALTER TABLE "Pastes" CHANGE "EditDate" "edit_date" VARCHAR(1000000);
ALTER TABLE "Pastes" CHANGE "EditPassword" "edit_password" VARCHAR(1000000);
ALTER TABLE "Pastes" CHANGE "Metadata" "metadata" VARCHAR(1000000);

Then you can just set the value of metadata to the default for all pastes (fix deserialization error):

{"owner":"","private_source":"off","title":"","description":"","favicon":null,"embed_color":"#ff9999"}

You'll also have to add the id column. This column normally has a random value, but you could technically set it to be the same as the custom_url and you'll have no issues.

*Technically* it's possible, the schema is essentially the same with the only difference really being column names and 1 or 2 extras. ![image](/attachments/f45875fd-2758-42c3-8c49-748e6482535d) ![image](/attachments/ef469c61-79d7-4923-ad92-e31df9fba883) Depending on the number of pastes you're migrating this could be pretty easy or pretty hard. Pastes would have to be re-rendered and have that value filled into the `content_html` column (from new schema), and `GroupSubmitPassword` would have to just be dropped entirely. `Metadata` would also likely have to be dropped as many of the [fields](https://stellular.net/api/docs/bundlrs/db/bundlesdb/struct.PasteMetadata.html) are different now. Honestly you could likely just import all data and run the following SQL commands (untested, so you should probably review them): ```sql ALTER TABLE "Pastes" CHANGE "CustomURL" "custom_url" VARCHAR(1000000); ALTER TABLE "Pastes" CHANGE "GroupName" "group_name" VARCHAR(1000000); ALTER TABLE "Pastes" CHANGE "PubDate" "pub_date" VARCHAR(1000000); ALTER TABLE "Pastes" CHANGE "EditDate" "edit_date" VARCHAR(1000000); ALTER TABLE "Pastes" CHANGE "EditPassword" "edit_password" VARCHAR(1000000); ALTER TABLE "Pastes" CHANGE "Metadata" "metadata" VARCHAR(1000000); ``` Then you can just set the value of `metadata` to the default for all pastes (fix deserialization error): ```json {"owner":"","private_source":"off","title":"","description":"","favicon":null,"embed_color":"#ff9999"} ``` You'll also have to add the `id` column. This column normally has a random value, but you could technically set it to be the same as the `custom_url` and you'll have no issues.

image.png

29 KiB

image.png

44 KiB

👍 1