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: bug empty relations in view #2784

Closed
lublak opened this issue Jul 21, 2022 · 2 comments
Closed

馃悰 Bug: bug empty relations in view #2784

lublak opened this issue Jul 21, 2022 · 2 comments
Labels
馃憢 For : Community or Good First Issue Targeting community to contribute 馃悰 Type: Bug Something is broken or incorrect unexpectedly.

Comments

@lublak
Copy link

lublak commented Jul 21, 2022

Please enter the following details

Node: **v16.15.0**
Arch: **x64**
Platform: **win32**
Docker: **false**
Database: **pg**
ProjectOnRootDB: **false**
RootDB: **sqlite3**
PackageVersion: **0.92.4**

Steps To Reproduce

  1. Create a new project from external data source
  2. Use postgres
  3. Use following ddls
CREATE TABLE purchasing (
    id int4 NOT NULL GENERATED BY DEFAULT AS IDENTITY,
    mandant_id int2 NOT NULL,
    company_code int4 NOT NULL,
    sequence_number int8 NOT NULL,
    "year" int2 NOT NULL,
    "month" int2 NOT NULL,
    CONSTRAINT purchasing_check_month CHECK (((month >= 1) AND (month <= 12))),
    CONSTRAINT purchasing_check_year CHECK (((year >= 2000) AND (year <= 2100))),
    CONSTRAINT purchasing_client_plant_sequence_number_key UNIQUE (mandant_id, company_code, sequence_number),
    CONSTRAINT purchasing_pkey PRIMARY KEY (id)
);
CREATE INDEX purchasing_id_idx ON purchasing USING btree (id);
ALTER TABLE purchasing ADD CONSTRAINT purchasing_company_code_fk FOREIGN KEY (company_code) REFERENCES company_codes(id);
ALTER TABLE purchasing ADD CONSTRAINT purchasing_mandant_id_fkey FOREIGN KEY (mandant_id) REFERENCES purchasing_mandant_names(id) NOT VALID;
CREATE TABLE purchasing_pages (
    purchasing_id int8 NOT NULL,
    page_path varchar(255) NOT NULL,
    CONSTRAINT purchasing_pages_check_page_path CHECK (((page_path)::text ~ '^([a-zA-Z0-9\-_ ]+\/)+[a-zA-Z0-9\-_ ~]+\.[tT][iI][fF]'::text)),
    CONSTRAINT purchasing_pages_purchasing_id_page_path_key UNIQUE (purchasing_id, page_path)
);

ALTER TABLE purchasing_pages ADD CONSTRAINT purchasing_pages_id_fkey FOREIGN KEY (purchasing_id) REFERENCES purchasing(id) ON UPDATE CASCADE ON DELETE RESTRICT;

Expected Behavior

it should link to the right pages here and not just be blank

Screenshots

grafik
grafik
grafik

@o1lab o1lab added 馃悰 Type: Bug Something is broken or incorrect unexpectedly. 馃攷 Status: More Info Needed More information is required to figure out the root cause. 馃憢 For : Community or Good First Issue Targeting community to contribute labels Sep 13, 2022
@wingkwong wingkwong removed the 馃攷 Status: More Info Needed More information is required to figure out the root cause. label Jan 7, 2023
@o1lab o1lab changed the title bug empty releations in view 馃悰 Bug: bug empty releations in view Jan 7, 2023
@o1lab o1lab changed the title 馃悰 Bug: bug empty releations in view 馃悰 Bug: bug empty relations in view Jan 11, 2023
@pranavxc pranavxc self-assigned this Jan 16, 2023
@pranavxc
Copy link
Member

pranavxc commented Jan 16, 2023

In the second table, there is no primary key present, in order to work all Nocodb APIs both tables should have a primary key.

@pranavxc pranavxc removed their assignment Jan 16, 2023
@dstala
Copy link
Member

dstala commented Feb 16, 2023

@lublak please reopen if you think this still needs attention

@dstala dstala closed this as not planned Won't fix, can't repro, duplicate, stale Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
馃憢 For : Community or Good First Issue Targeting community to contribute 馃悰 Type: Bug Something is broken or incorrect unexpectedly.
Projects
None yet
Development

No branches or pull requests

5 participants