Tweet
First, i love the UI upgrade and i can finally have materialized views in a proper place. FINALLY queries can be saved and loaded in a sane fashion : But:
1) Browsing any tables in a schema constantly throws '##################' is not a valid integer value. This message pops up once for every row in the table, and i have millions of rows. The primary key on these tables are 18 digit numbers, marked int8. The same data in other schemas randomly has this happen as well
I must hard kill navicat to continue. Seems to only affect schemas with views ? This is not a problem at all in 11, and the values / tables are 100% Postgres compatible and legal
2) browsing tables (Double click, 1000 record sample) displays an error that table 'X' does not have a primary key. This table, and every other one, 100% has a primary key. The user I am browsing with has full rights to these tables.
So far issue 1 is a showstopper killing my daily work, and I havent even gotten further to test becuase if it
1) Browsing any tables in a schema constantly throws '##################' is not a valid integer value. This message pops up once for every row in the table, and i have millions of rows. The primary key on these tables are 18 digit numbers, marked int8. The same data in other schemas randomly has this happen as well
I must hard kill navicat to continue. Seems to only affect schemas with views ? This is not a problem at all in 11, and the values / tables are 100% Postgres compatible and legal
2) browsing tables (Double click, 1000 record sample) displays an error that table 'X' does not have a primary key. This table, and every other one, 100% has a primary key. The user I am browsing with has full rights to these tables.
So far issue 1 is a showstopper killing my daily work, and I havent even gotten further to test becuase if it
Comment