When the target table for a foreign key constraint has a multi-column primary key, the generated constraint seems to list the keys in alphabetical order instead of column ordinal order. This causes resulting joins to match zero records.
Comments: Fixed. This will be in the next release.
Comments: Fixed. This will be in the next release.