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: Api linked fields duplicated #7020

Closed
1 task done
emre1e opened this issue Nov 17, 2023 · 8 comments 路 Fixed by #7030
Closed
1 task done

馃悰 Bug: Api linked fields duplicated #7020

emre1e opened this issue Nov 17, 2023 · 8 comments 路 Fixed by #7030
Assignees
Labels
馃悰 Type: Bug Something is broken or incorrect unexpectedly.

Comments

@emre1e
Copy link

emre1e commented Nov 17, 2023

Please confirm if bug report does NOT exists already ?

  • I confirm there is no existing issue for this

Steps to reproduce ?

excecute the get api in Version 2 or version 1

Results in linked tables are duplicated, even only 1 link is selected

New in 202.7

image

Desired Behavior

should only show once like before the update

image

Project Details

Node: v18.17.1
Arch: x64
Platform: linux
Docker: true
RootDB: pg
PackageVersion: 0.202.7

Attachments

No response

@dstala
Copy link
Member

dstala commented Nov 17, 2023

  • Is this problem noticed after migration?
  • Which data type are you using to create relations - "Links" or "LinkToAnotherRecord"?
  • What's your relation type : has-many or many-many?
  • Does this issue happen even for a newly created table?

We tried under same environment as your's Docker + PG, but we were unable to reproduce it yet.

@emre1e
Copy link
Author

emre1e commented Nov 17, 2023

im just excecuting the get api. All linked fields are duplicated. Example:

image

@emre1e
Copy link
Author

emre1e commented Nov 17, 2023

Forgot what i said...

after the migration somehow all linked entries are duplicated.

Did you had a script to migrate linktoanotherrecord fields to links fields?

@dstala
Copy link
Member

dstala commented Nov 17, 2023

Did you had a script to migrate linktoanotherrecord fields to links fields?

No. Migrations were not enforced. We had left LTAR fields as is. Links type was introduced additionally.

@emre1e
Copy link
Author

emre1e commented Nov 17, 2023

ok then something is really wrong in the api.

Linktoanother records are duplicated.

links are fine.

In the database its correct for both.

image

@pranavxc
Copy link
Member

Hi I've few queries which may help us to debug.

  • From which version did you migrated to the latest ?
  • Is there multiple entry in the actual db ?
  • Which relation type are you using (has many / many to many) ?
  • Are you using Redis for caching ?
  • If you add new row to the existing link column does it getting duplicated ?

@dstala
Copy link
Member

dstala commented Nov 17, 2023

@emre1e if you are available, you can DM @pranavxc on discord for quick sync.
Discord ID : pranavxc#7398
Discord : https://discord.gg/5RgZmkW

@emre1e
Copy link
Author

emre1e commented Nov 17, 2023

From which version did you migrated to the latest ? --> 202.5
Is there multiple entry in the actual db ? --> no
Which relation type are you using (has many / many to many) ? --> many to many
Are you using Redis for caching ? --> yes
If you add new row to the existing link column does it getting duplicated ? --> no because with the new relation links its working

@wingkwong wingkwong added this to the v0.203.0 milestone Nov 20, 2023
@wingkwong wingkwong added the 馃悰 Type: Bug Something is broken or incorrect unexpectedly. label Nov 20, 2023
@dstala dstala removed this from the vFeature milestone Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
馃悰 Type: Bug Something is broken or incorrect unexpectedly.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants