NocoDB loosing connection to other table after syncing meta data #1009

WeT-Klb · 2022-01-26T14:13:41Z

Node: v12.22.6
Arch: x64
Platform: linux
Docker: true
Database: mysql2
ProjectOnRootDB: true
RootDB: mysql2
PackageVersion: 0.84.8
Project was created by clicking : Create New Project
OS on which NocoDB is running : QNAP 5.0.0.1891
Database version : MariaDB 10.5

Steps To Reproduce

Go to table 'Arztadressen`, set name field to "Primary Value" and create a connection to table 'Impfbuch_Mian'
Go to table 'Impfbuch_Mian' and creaty lookup entries to 'Arztadressen'
Click on refresh tables or 'Sync Now' in meta file data
The connection between both tables gets lost and in 'Impfbuch_Mian' the conection field type changes
The "Primary entry setting" in 'Arztadressen' got lost, too.

Expected behavior
A refresh of tables or a sync shouldn´t change the ralation.

Screenshots
I

Join our discord : https://discord.gg/5RgZmkW for realtime help.

o1lab · 2022-01-26T14:42:04Z

Looks like you have created the same database in NC_DB to create a project by connecting to external database.

This is not an intended usecase.

NC_DB and Project creation by connecting to external database should be seperate.

o1lab · 2022-01-26T14:49:57Z

Im unable to reproduce the issue. Can you reach out to me in discord.

WeT-Klb · 2022-01-26T15:58:56Z

I can´t reach out in discord as i´m always told the invitation has expired. Is it Possible to contact me through email? Von: navi ***@***.*** Gesendet: Mittwoch, 26. Januar 2022 15:50 An: nocodb/nocodb Cc: Werner; Author Betreff: Re: [nocodb/nocodb] NocoDB loosing connection to other table (Issue #1009) Im unable to reproduce the issue. Can you reach out to me in discord <https://discord.gg/5RgZmkW> . — Reply to this email directly, view it on GitHub <#1009 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5FMFVCWIMHI2QODBQC2XLUYAC2BANCNFSM5M3ETJRQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AE5FMFQVI7NSR7VWU6LOLTTUYAC2BA5CNFSM5M3ETJR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHTXJRVI.gif> Message ID: ***@***.***>

o1lab · 2022-01-26T16:21:07Z

Please reach out at n at nocodb.com

WeT-Klb · 2022-01-26T21:21:23Z

I deleted the whole project, deleted the data base and restarted from the scratch with building everything new.
First i choose "Create" instead of "Create with external data base". Then i addes the three tables which i exported before from old data base and in field mapping i deleted everything showing a connection to another sheet.
Then i set table connections and set up everything like it should be. But again in meta files i am shown the connections were released. I don´t dare to click on "Sync now" as i guess again everything will be screwed up.

EDIT 30.1.2022
Ok - i tried what happens after i click "Sync Now". The result is the "Link to another record" from "Arztpraxis" to "Impfbuch_Mian" and "Impfbuch_Werner" got lost again and the primary key in "Arztadressen" resetted.
The entries in both "Impfbuch"-tables looks like this now:

As long as the marked row exists it is impossible to recreate a "Link to another record" to this table - first this row has to be deleted.
Then after recreating the link and syncing the metadata again the same behaviour like before where the link has gone.

WeT-Klb · 2022-01-27T13:59:42Z

Please reach out at n at nocodb.com

Do you want me to send an email to P-at-nocodb.com?
Discord always tells me the invitation has expired.

o1lab · 2022-01-27T18:30:58Z

It is n at nocodb.com :)

Thank you for letting us know discord link has an issue.

Here is another invite link to discord : https://discord.gg/xT47QnTy

WeT-Klb · 2022-01-27T20:04:07Z

I tried your new invitation link - but still the same:

Yesterday and today i sent an email to "n @ nocodb.com" - did you get it?

o1lab · 2022-01-28T09:09:56Z

No idea on discord expiry, I tried those links to be sure. They worked.

Meantime you can book a time here calendly.com/nocodb

o1lab · 2022-01-28T09:10:43Z

Sorry, I havent received any email so far.

WeT-Klb · 2022-01-28T09:23:55Z

This is what i sent yesterday:

This what is shown to me when i check "Why my invitation is invalid?":

Invalid Invite Links
 Tann
2 months ago Updated
You finally got that invite to the super-secret Discord server you've been wanting to join, yes!

So... why isn't it working? There are a few reasons your server link may be 'Invalid'.

WHAT TO CHECK
Expiration: Your invite link may have expired. In this case, please contact the server owner and ask them for a new invite.

Invalid Code: You may not have a legitimate invite code. Please check your code and try again. Remember that invite codes -are- case sensitive!

Ban: You may have been banned from joining this server. Bans are based on IP address, so you would need to contact the server admins and ask them to revoke all bans in their Server Settings. Just because they remove your name, does not mean the invite will work.

100 Server Limit: A user cannot be a member of more than 100 servers. If you are in too many servers, you'll need to leave one before you can join.

WeT-Klb · 2022-03-10T10:19:29Z

I still have that problem with "Sync Now". NocoDB still tells me the relation between the tables was removed - but this is not true.
Still "Arztadresse" is the parent table and the both "Impfbuch" are the child table - at least that´s what i want and like it works.

o1lab · 2022-03-10T10:53:03Z

Can you please project info. Do you suspect anything that might have led to this ?

Please DM in discord, happy to help.

WeT-Klb · 2022-03-10T11:12:28Z

The project info is:

Node: v12.22.6
Arch: x64
Platform: linux (QNAP 5.0.0.1932)
Docker: true
Database: mysql2 (MariaDB 10.5.8)
ProjectOnRootDB: true
RootDB: mysql2
PackageVersion: 0.84.14

I have no idea what can cause this - but it already happened in january (when i started with NocoDB) - with all releases since then.
Every time after pressing "Sync Now" the connections between the tables will be destroyed.
Again i have trouble with Discord - this time it tells me they registered a Log-In from a different location and i would need to see the Email they sent - but no Mail apperas yet. Always trouble with Discord :-(

o1lab · 2022-03-10T13:28:26Z

Were there database changes done externally on your database which made you sync meta changes ?

And with Discord : would you like to access the same with a different browser - it looks like Discord may be flagging something on your end.

WeT-Klb · 2022-03-10T13:46:39Z

No - I created the first table "Arztadressen" then I created the two "Impfbuch"-tables. Until this everything was ok. Then I created the connection between "Arztadressen" and the two "Impfbuch" . In "Arztadressen" I set "Name" as primary key. And always after using data from "Arztadressen" in "Impfbuch" I will get this problem. Only thing I forgot at the beginning was to set external drive for making attachments persistent - but this shouldn´t affect the relation between the tables, right?

o1lab · 2022-03-10T13:49:37Z

Have mailed you a zoom link - pls join. Happy to help.

o1lab · 2022-03-10T14:44:27Z

Thanks for showing the problem and sharing the relevant files.

Would be also helpful to know the MariaDB version.

Looks like the issue might be to do with mariadb as same scenario was fine on PG. I will add more details here later.

WeT-Klb · 2022-03-10T14:53:10Z

Is it this you are looking for? ![NocoDB](https://user-images.githubusercontent.com/20600342/157688144-e0197a85-33c2-41eb-abfb-ee7648a1c61c.jpg)

WeT-Klb · 2022-03-31T09:50:52Z

@o1lab
Did you find any solution? This problem still exists even with latest docker version of NocoDB.

WeT-Klb · 2022-04-18T17:30:30Z

I still have this same behaviour in 0.90.3 now. Do you think there will be any solution for this?

wingkwong · 2022-04-19T10:38:19Z

@WeT-Klb I tried to follow your screenshots to reproduce the issue. After following the first two screenshots, it leads me to the following screen where it shows the metadata is in sync. Your third screenshot shows no change identified but Sync Now button is enabled which is not expected.

As it's hard to trace back in previous versions, if you create a new project at 0.90.3 and do the same thing again, are you able to reproduce the issue? You may try creating a brand new project and connect to existing one.

If you have discord, please feel free to reach me (same username) or you can reach me at w@nocodb.com via email.

dstala · 2023-09-01T05:04:39Z

@WeT-Klb reopen or connect with us in discord if issue still persists

WeT-Klb changed the title ~~NocoDB loosing connection to other table~~ NocoDB loosing connection to other table after syncing meta data Jan 31, 2022

wingkwong self-assigned this Apr 19, 2022

nocodb deleted a comment from o1lab Apr 19, 2022

o1lab added the 👋 For : Community or Good First Issue Targeting community to contribute label Sep 13, 2022

wingkwong removed their assignment Nov 11, 2022

lcavasso mentioned this issue Jun 21, 2023

🐛 Bug: Syncing NC_DB metadata removes visibility to all tables from external DB #5944

Closed

1 task

dstala closed this as completed Sep 1, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

NocoDB loosing connection to other table after syncing meta data #1009

NocoDB loosing connection to other table after syncing meta data #1009

WeT-Klb commented Jan 26, 2022 •

edited

o1lab commented Jan 26, 2022

o1lab commented Jan 26, 2022

WeT-Klb commented Jan 26, 2022 via email •

edited

o1lab commented Jan 26, 2022

WeT-Klb commented Jan 26, 2022 •

edited

WeT-Klb commented Jan 27, 2022 •

edited

o1lab commented Jan 27, 2022

WeT-Klb commented Jan 27, 2022

o1lab commented Jan 28, 2022

o1lab commented Jan 28, 2022

WeT-Klb commented Jan 28, 2022 •

edited

WeT-Klb commented Mar 10, 2022

o1lab commented Mar 10, 2022

WeT-Klb commented Mar 10, 2022 •

edited

o1lab commented Mar 10, 2022 •

edited

WeT-Klb commented Mar 10, 2022 via email

o1lab commented Mar 10, 2022

o1lab commented Mar 10, 2022 •

edited

WeT-Klb commented Mar 10, 2022 via email •

edited

WeT-Klb commented Mar 31, 2022

WeT-Klb commented Apr 18, 2022

wingkwong commented Apr 19, 2022

dstala commented Sep 1, 2023

NocoDB loosing connection to other table after syncing meta data #1009

NocoDB loosing connection to other table after syncing meta data #1009

Comments

WeT-Klb commented Jan 26, 2022 • edited

o1lab commented Jan 26, 2022

o1lab commented Jan 26, 2022

WeT-Klb commented Jan 26, 2022 via email • edited

o1lab commented Jan 26, 2022

WeT-Klb commented Jan 26, 2022 • edited

WeT-Klb commented Jan 27, 2022 • edited

o1lab commented Jan 27, 2022

WeT-Klb commented Jan 27, 2022

o1lab commented Jan 28, 2022

o1lab commented Jan 28, 2022

WeT-Klb commented Jan 28, 2022 • edited

WeT-Klb commented Mar 10, 2022

o1lab commented Mar 10, 2022

WeT-Klb commented Mar 10, 2022 • edited

o1lab commented Mar 10, 2022 • edited

WeT-Klb commented Mar 10, 2022 via email

o1lab commented Mar 10, 2022

o1lab commented Mar 10, 2022 • edited

WeT-Klb commented Mar 10, 2022 via email • edited

WeT-Klb commented Mar 31, 2022

WeT-Klb commented Apr 18, 2022

wingkwong commented Apr 19, 2022

dstala commented Sep 1, 2023

WeT-Klb commented Jan 26, 2022 •

edited

WeT-Klb commented Jan 26, 2022 via email •

edited

WeT-Klb commented Jan 26, 2022 •

edited

WeT-Klb commented Jan 27, 2022 •

edited

WeT-Klb commented Jan 28, 2022 •

edited

WeT-Klb commented Mar 10, 2022 •

edited

o1lab commented Mar 10, 2022 •

edited

o1lab commented Mar 10, 2022 •

edited

WeT-Klb commented Mar 10, 2022 via email •

edited