Opened 10 years ago
#899 new defect
PostgreSQL provider does not support other schema than public when fdometadata is activated
Reported by: | bscott | Owned by: | badreddinekaroui |
---|---|---|---|
Priority: | blocker | Milestone: | 3.8.0 |
Component: | PostgreSQL Provider | Version: | 3.8.0 |
Severity: | 3 | Keywords: | |
Cc: | External ID: |
Description
To be able to insert/update data into a view, FDO require a primary key. With Oracle we can set a disable unique pkey constraint, with SQLServer we can use a view with schema binding but with PostgreSQL there is no workaround to make FDO find a primary key.
The only way i've found is to populate all the fdo metadata tables. Works fine except if the client tables belongs to another schema than public.
Included is a patch that fix this issue. The patch has been created on the Utilities directory
Attachments (1)
Note:
See TracTickets
for help on using tickets.