Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Bug: M2M tables without content after update #7158

Closed
1 task done
j-stahl opened this issue Dec 5, 2023 · 3 comments 路 Fixed by #7161
Closed
1 task done

馃悰 Bug: M2M tables without content after update #7158

j-stahl opened this issue Dec 5, 2023 · 3 comments 路 Fixed by #7161
Assignees

Comments

@j-stahl
Copy link

j-stahl commented Dec 5, 2023

Please confirm if bug report does NOT exists already ?

  • I confirm there is no existing issue for this

Steps to reproduce ?

Hard to say, if you can really reproduce it. It is a migration problem.

I have 2 tables named images and products with a M2M connection between them. After upgrading from NocoDB 0.96.4 the first view on the data looks great. On a deeper look, I realised the column with the m2m table is empty in both tables.
grafik

While NocoDB obviously knows, there are links. On clicking the plus button for adding new linked records, I can see this:
grafik

When I try to add data with the web interface, this is basically possible. The MySQL table shows new records appearing inside, but the result is not visible in the web frontend.

The HTTP Response from the server, shows there are empty objects for m2m tables, while another hm/bt table delivers object id's. The same result, I can see, when I use the REST API with my own app.
grafik

When I create a brand new test base with 2 test tables. The relations between both tables will be shown correctly. In the linked column appears an information. Which means basically the new software seems to work properly on new bases and tables.
grafik

I have only this one M2M relation between the tables and I want to repair it. Sadly I do not know how NocoDB realizes the relations, and where I can start search for the source of this issue.

Desired Behavior

After the NocoDB update the data should be migrated correctly and be available in the view in the same way new created data is.

Project Details

Node: v18.17.1
Arch: x64
Platform: linux
Docker: true
RootDB: mysql2
PackageVersion: 0.202.9

Attachments

No response

@pranavxc
Copy link
Member

pranavxc commented Dec 5, 2023

We had made a fix, please try the following PR build to verify the fix.

docker run -d -p 8888:8080 nocodb/nocodb-timely:0.202.9-pr-7161-20231205-1350

@pranavxc
Copy link
Member

pranavxc commented Dec 5, 2023

Duplicate of #7125

@pranavxc pranavxc marked this as a duplicate of #7125 Dec 5, 2023
@pranavxc pranavxc closed this as completed Dec 5, 2023
@pranavxc pranavxc assigned pranavxc and unassigned o1lab Dec 6, 2023
@j-stahl
Copy link
Author

j-stahl commented Dec 8, 2023

YES! That's it. Good work.
The image you mentioned worked for me.

When do you expect the next official release containing this fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants