This question is locked. New answers and comments are not allowed.
Hi,
I received the following error when trying to create an entity model from PostgreSQL database
Unable to retrieve the database schema information.
Reason: Not all of the primary key columns were found on table '...'
What does this error mean, and any suggestion on how to resolve it?
Thanks
Jackie
I received the following error when trying to create an entity model from PostgreSQL database
Unable to retrieve the database schema information.
Reason: Not all of the primary key columns were found on table '...'
What does this error mean, and any suggestion on how to resolve it?
Thanks
Jackie
5 Answers, 1 is accepted
0
Hi Wenrong,
Kind regards,
Ady
the Telerik team
This error indicates that while reading the primary keys for a table OpenAccess detected that there are 'x' number of columns in the primary key but it could not find all these 'x' column in the table. The table name looks wierd though - '...'. Do you have a peculiar table name in your database?
Can you send us your database or any tables with a strange/peculiar name? This will help us in reproducing the error locally.
Kind regards,
Ady
the Telerik team
Follow @OpenAccessORM Twitter channel to get first the latest updates on new releases, tips and tricks and sneak peeks at our product labs!
0
Wenrong
Top achievements
Rank 1
answered on 03 May 2012, 10:31 AM
Sorry, I used '...' to hide the table name I used.
I tried to reproduce this issue with a simpler database. It seems to happen when the primary key is renamed. The following should reproduce it:
I tried to reproduce this issue with a simpler database. It seems to happen when the primary key is renamed. The following should reproduce it:
CREATE
TABLE
test
(
test_id SERIAL
NOT
NULL
,
test_name
char
(32)
NOT
NULL
,
CONSTRAINT
pk_test
PRIMARY
KEY
(test_id)
);
ALTER
TABLE
test
RENAME test_id
TO
test_id1;
0
Wenrong
Top achievements
Rank 1
answered on 07 May 2012, 05:54 AM
Any solution regarding this issue?
0
Accepted
Hello Wenrong,
We have fixed this problem and the fix will be available in the Q2 release (due in the first half of June). I'm afraid there is no workaround for this at the moment.
I'm sorry for the inconvenience caused.
Regards,
Ady
the Telerik team
We have fixed this problem and the fix will be available in the Q2 release (due in the first half of June). I'm afraid there is no workaround for this at the moment.
I'm sorry for the inconvenience caused.
Regards,
Ady
the Telerik team
Follow @OpenAccessORM Twitter channel to get first the latest updates on new releases, tips and tricks and sneak peeks at our product labs!
0
Wenrong
Top achievements
Rank 1
answered on 07 May 2012, 08:42 PM
OK, that's fine.