Linked objects representation :[Sep 30]

Discord-Discussions
1

:raising_hand_man: hell_io asked

Got a problem with ‘invisible’ links to another table. The column looks empty, though if I expand a concrete cell I can see a list of related rows. Maybe it has something to do with custom id column

2

:raising_hand_man: elephantum replied

image0

3

:raising_hand_man: elephantum replied

image0
image0615×633 37.1 KB

4

:person_tipping_hand: o1lab replied

We automatically choose a primary value column for the linkToAnoterRecord

Could you please check if tehre is an empty column in another table

If so, please select some other column as primary value column - this can be done by hovering on column header. And then you can come and refresh the page

5

:raising_hand_man: hell_io replied

The primary value column is not empty, every row has a value and it’s a text ID (non-null, pk). Renaming column from custom name to “id” doesn’t help, unfortunately

6

:raising_hand_man: hell_io replied

There’s another interesting problem, you can see it in the first pic, the right column. The values are all the same and don’t make sense cause the primary values in the related table are text IDs as well

7

:raising_hand_man: elephantum replied

Selecting primary value does not help, just tried it couple of times. :frowning_with_open_mouth:

8

:raising_hand_man: elephantum replied

Right column of data looks like unix timestamp, actually

9

:person_tipping_hand: o1lab replied

possible to do a quick zoom ?

10

:person_tipping_hand: o1lab replied

will help see the problem quick

11

:raising_hand_man: elephantum replied

hell_io@discord up to you

12

:person_tipping_hand: o1lab replied

can u please paste the project info (from top right menu)

13

:raising_hand_man: elephantum replied

Node: v12.22.1

Arch: x64

Platform: linux

Docker: false

Database: pg

ProjectOnRootDB: true

RootDB: pg

PackageVersion: 0.11.29

14

:raising_hand_man: elephantum replied

> Docker: false

is not true, we run nocodb in docker in k8s

15

:raising_hand_man: hell_io replied

we might have figured out, that we just shouldn’t write rows to the database directly, but only via API. Maybe It’s kinda obvious

So for now I’m gonna try and insert data correctly, and if doesn’t work out - let’s zoom then

16

:person_tipping_hand: o1lab replied

ohok

17

:person_tipping_hand: o1lab replied

ok

18

:person_tipping_hand: o1lab replied

writing rows is fine - we just read the rows

however, if you are changing schema - then it has to be synced

19

:person_tipping_hand: o1lab replied

https://docs.nocodb.com/setup-and-usages/sync-schema

20

:person_tipping_hand: o1lab replied

caution : although this will break things related to schema migrations from env to another