Version: 1.1.3 (KOffice 1.6.3) (using KDE KDE 3.5.8) Installed from: Ubuntu Packages OS: Linux Kexi 1.1.3 running on Ubuntu laptop, Sample postgresql database on linux server (local network). Since Kexi will not open original db, it is imported and saved on same server as original. the following is a sample of one table only from the original and the imported version (sql provided by pgAdmin3). I am only but a newbie and suspect that many differences between the tables have no consequences, but the "NOT NULL" I believe should not disappear?. Hats off to everyone working on Kexi - slogan should read "Better than Microsoft Access for Linux" thanks :-)Dave -----------------original table ------------------------- -- Table: gltx -- DROP TABLE gltx; CREATE TABLE gltx ( gltx_id numeric(18) NOT NULL, version int4 NOT NULL, created_by varchar(16) NOT NULL, updated_by varchar(16), inactive_by varchar(16), created_on date NOT NULL, updated_on date, inactive_on date, external_id numeric(14), data_type int4 NOT NULL, number varchar(14) NOT NULL, reference_str varchar(14), post_date date NOT NULL, post_time time NOT NULL, memo varchar(40), card_id numeric(18), station_id numeric(18), employee_id numeric(18), store_id numeric(18) NOT NULL, shift_id numeric(18), link_id numeric(18), printed char(1) NOT NULL, paid char(1) NOT NULL, amount numeric(18,4) NOT NULL, CONSTRAINT gltx_pkey PRIMARY KEY (gltx_id), CONSTRAINT gltx_card_id_fkey FOREIGN KEY (card_id) REFERENCES card (card_id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE NO ACTION, CONSTRAINT gltx_employee_id_fkey FOREIGN KEY (employee_id) REFERENCES card (card_id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE NO ACTION, CONSTRAINT gltx_link_id_fkey FOREIGN KEY (link_id) REFERENCES gltx (gltx_id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE SET NULL, CONSTRAINT gltx_shift_id_fkey FOREIGN KEY (shift_id) REFERENCES gltx (gltx_id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE NO ACTION, CONSTRAINT gltx_station_id_fkey FOREIGN KEY (station_id) REFERENCES station (station_id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE NO ACTION, CONSTRAINT gltx_store_id_fkey FOREIGN KEY (store_id) REFERENCES store (store_id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE NO ACTION ) WITHOUT OIDS; ALTER TABLE gltx OWNER TO quasar_dba; GRANT ALL ON TABLE gltx TO quasar_dba; GRANT SELECT, UPDATE, INSERT, DELETE ON TABLE gltx TO quasar; -- Index: gltx_i0 -- DROP INDEX gltx_i0; CREATE INDEX gltx_i0 ON gltx USING btree (data_type); -- Index: gltx_i1 -- DROP INDEX gltx_i1; CREATE INDEX gltx_i1 ON gltx USING btree (post_date); -- Index: gltx_i2 -- DROP INDEX gltx_i2; CREATE INDEX gltx_i2 ON gltx USING btree (number); -- Index: gltx_i3 -- DROP INDEX gltx_i3; CREATE INDEX gltx_i3 ON gltx USING btree (data_type, number); -- Index: gltx_i4 -- DROP INDEX gltx_i4; CREATE INDEX gltx_i4 ON gltx USING btree (card_id, paid); ------------------------------------------------------------------------- -----------------imported table ----------------------------------------- -- Table: gltx -- DROP TABLE gltx; CREATE TABLE gltx ( gltx_id float8 NOT NULL, version int4, created_by varchar(200), updated_by varchar(200), inactive_by varchar(200), created_on date, updated_on date, inactive_on date, external_id float8, data_type int4, number varchar(200), reference_str varchar(200), post_date date, post_time time, memo varchar(200), card_id float8, station_id float8, employee_id float8, store_id float8, shift_id float8, link_id float8, printed varchar(200), paid varchar(200), amount float8, CONSTRAINT gltx_pkey PRIMARY KEY (gltx_id) ) WITH OIDS; ALTER TABLE gltx OWNER TO quasar_dba;
Old report but still makes perfect sense to check that.
In Kexi 3 we want to support databases directly, without importing them. Then issues like this would disappear.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.