Raph Comments - Answer Overflow

Topics

Raph

•Created by oyiks on 12/24/2024 in #❓︱help

database reset error.

I believe you're at a ram limitation. Look around within discord and you'll see others that are running locally running into the same issues.

8 replies

•Created by ParallelPlatypus on 12/17/2024 in #❓︱help

Version 0.34 migration causing issues on production deployment due to subdomain

I also ran into this issue, but also with a foreign key constraint on a user that was used to create the user workspace. In that case I wasn’t able to delete the workspace. If the workspace has a user associated with the workspace you will not be able to delete the workspace. So, obviously you should back up your db before performing any manual queries. After you’ve backed up you can run a pg query like:

DELETE FROM core.user WHERE id IN ('20202020-1c25-4d02-bf25-6aeccf7ea419’)

DELETE FROM core.user WHERE id IN ('20202020-1c25-4d02-bf25-6aeccf7ea419’)

You would need to do this BEFORE running @AMoreaux ’s query to delete the workspace only if a user is associated with it:

DELETE FROM core.workspace WHERE id IN ('20202020-1c25-4d02-bf25-6aeccf7ea419', '3b8e6458-5fc1-4e63-8563-008ccddaa6db')

DELETE FROM core.workspace WHERE id IN ('20202020-1c25-4d02-bf25-6aeccf7ea419', '3b8e6458-5fc1-4e63-8563-008ccddaa6db')

5 replies

•Created by ParallelPlatypus on 12/17/2024 in #❓︱help

Version 0.34 migration causing issues on production deployment due to subdomain

In the comment section in the above github issue you'll see that there are a few queries that are used to remove those workspaces.

5 replies

•Created by ParallelPlatypus on 12/17/2024 in #❓︱help

Version 0.34 migration causing issues on production deployment due to subdomain

Hey @ParallelPlatypus I had a similar issue. It stemmed from having multiple workspaces in your DB (probably by accident or through experimentation). You'll need to delete the other workspaces that you're not using.

5 replies

•Created by Raph on 12/23/2024 in #❓︱help

Data model - N:N Relationships on Custom Objects

Thanks to @bob 🍻

18 replies

•Created by Raph on 12/23/2024 in #❓︱help

Data model - N:N Relationships on Custom Objects

For those that care, I settled on the 1:N relationships. This allows me to have 1 person owning many deals.

18 replies

•Created by Raph on 12/23/2024 in #❓︱help

Data model - N:N Relationships on Custom Objects

Ok, so I tested that theory. Can I send you a DM with a video?

18 replies

•Created by Raph on 12/23/2024 in #❓︱help

Data model - N:N Relationships on Custom Objects

Changed the post to better reflect the discussion.

18 replies

•Created by Raph on 12/23/2024 in #❓︱help

Data model - N:N Relationships on Custom Objects

ok, so the limitation here is that 1 person can have many deals. However, many people can't have many deals.

18 replies

•Created by Raph on 12/23/2024 in #❓︱help

Data model - N:N Relationships on Custom Objects

yup

18 replies

•Created by Raph on 12/23/2024 in #❓︱help

Data model - N:N Relationships on Custom Objects

🤔 might be M:M

18 replies

•Created by Raph on 12/23/2024 in #❓︱help

Data model - N:N Relationships on Custom Objects

you're right..

18 replies

•Created by Raph on 12/23/2024 in #❓︱help

Data model - N:N Relationships on Custom Objects

Had that backwards 😅

18 replies

•Created by Raph on 12/23/2024 in #❓︱help

Data model - N:N Relationships on Custom Objects

Hi @bob - stepped away for a few mins. So looking to establish a Deal - to - Many People relationship.

18 replies

•Created by Raph on 12/21/2024 in #❓︱help

I think I may have suffered a migration regression for "phones". Migration from v.0.33 to v0.34

I did run a REINDEX here. All appears to be well. I don't see any errors.

53 replies

•Created by anjali on 12/23/2024 in #❓︱help

Database reset issue on V0.30.2

🤔 I haven't seen that one. Maybe try a REINDEX on the DB? Backup first obviosly...

4 replies

•Created by Raph on 12/21/2024 in #❓︱help

I think I may have suffered a migration regression for "phones". Migration from v.0.33 to v0.34

yes, all good. I'm just watching the logs looking for exceptions/etc

53 replies

•Created by Raph on 12/21/2024 in #❓︱help

I think I may have suffered a migration regression for "phones". Migration from v.0.33 to v0.34

Ok, back to the most recent state of Twenty. This is what I did to get the app back up. (Highly not recommended to mess with the DB manually):

ALTER TABLE IF EXISTS workspace_XXXXXXXXXXXXXX.person
    ADD COLUMN "phonesPrimaryPhoneNumber" text COLLATE pg_catalog."default" DEFAULT ''::text,
                "phonesPrimaryPhoneCountryCode" text COLLATE pg_catalog."default" DEFAULT ''::text,
                "phonesAdditionalPhones" jsonb;

ALTER TABLE IF EXISTS workspace_XXXXXXXXXXXXXX.person
    ADD COLUMN "phonesPrimaryPhoneNumber" text COLLATE pg_catalog."default" DEFAULT ''::text,
                "phonesPrimaryPhoneCountryCode" text COLLATE pg_catalog."default" DEFAULT ''::text,
                "phonesAdditionalPhones" jsonb;

53 replies

•Created by Raph on 12/21/2024 in #❓︱help

I think I may have suffered a migration regression for "phones". Migration from v.0.33 to v0.34

This is from an older backup of 33.7

53 replies