SQL Power Software Forum

Match Maker version 0.9.5 build #217, first spotted in 0.9.4
JRE 1.6.0_11
MatchMaker provided postgres JDBC driver
Accessing PostgreSQL 8.2
===================

The SQL generated for Postgres repository generation correctly qualifies all CREATE and ALTER commands with 'database_name.schema_name.', but fails to do so for the INSERT statements that populate initial table values. This results in a failure when a repository connection is later attempted by MatchMaker.

Exporting the generated SQL, making corrections and re-execution is an effective workaround.

The code subset below shows one correctly qualified object reference in an ALTER TABLE call, followed by INSERT statements with incomplete table qualifications as generated by the MatchMaker create repository dialog.

incorrecty generated code subset follows ==================================

...
ALTER TABLE data_quality.matchmaker.mm_munge_step_input ADD CONSTRAINT step_output_input_fk
FOREIGN KEY (munge_step_output_oid)
REFERENCES data_quality.matchmaker.mm_munge_step_output (munge_step_output_oid)
ON DELETE CASCADE
ON UPDATE CASCADE
DEFERRABLE INITIALLY DEFERRED;

insert into mm_schema_info values ('schema_version', '6.0.1')
;

INSERT INTO pl_group(group_name,group_desc,last_update_date,last_update_user,create_date)
VALUES('PL_ADMIN','Special PL group with ALL privileges',CURRENT_TIMESTAMP,'postgres',CURRENT_TIMESTAMP)
;

INSERT INTO pl_user (user_id, last_update_date, last_update_user,
default_kpi_frequency, show_red_ind, show_yellow_ind, show_green_ind, show_grey_ind)
VALUES (upper('postgres'), CURRENT_TIMESTAMP, 'postgres', 'MONTHLY', 'Y', 'Y', 'Y', 'Y')
;

INSERT INTO user_group (user_id, group_name, last_update_date, last_update_user)
VALUES (upper('postgres'), 'PL_ADMIN', CURRENT_TIMESTAMP, 'postgres')
;

This message was edited 1 time. Last update was at 2009-02-05 10:24:42

Hi again,

Ouch, looks like this is a real bug.

I was able to reproduce it when creating a repository in a schema other than 'public', which appears to be exactly what you did.

I created Bugzilla report here:
http://trillian.sqlpower.ca/bugzilla/show_bug.cgi?id=1763