Here it is with the interesting field names mangled for paranoia reasons:
db=# \d+ bpm.setupinfo;
Table
"bpm.setupinfo"
Column | Type |
Modifiers | Storage | Stats target | Description
-----------------------------+------------------------+--------------------------------------+----------+--------------+-------------
id | bigint | not null
| plain | |
clientid | bigint | not null
| plain | |
rxxxxxxxxxxx | character varying(40) |
| extended | |
ryyyyyyyyyyyyy | character varying(40) |
| extended | |
rzzzzzzzzzzzzzzzz | character varying(40) |
| extended | |
fxxxxxxxx | character varying(40) |
| extended | |
fyyyyyyy | character varying(40) |
| extended | |
fzzzzzzzzzz | character varying(40) |
| extended | |
sxxxxxxx | boolean | default false
| plain | |
onholdxxxx | character varying(20) |
| extended | |
wxxxxxxxxxxxxxxxxxxxxxxx | boolean | default false
| plain | |
encryxxxxxxxxxxxxxxxxxxxxx | character varying(100) |
| extended | |
encrypyyyyyyyyyyyyyy | character varying(100) |
| extended | |
cxxxxxxxxxxxxxxx | date |
| plain | |
projxxxxxxxxxxxxxxx | date |
| plain | |
has_existing_dxxxxxxxxxxxx | character varying(10) | default
'UNKNOWN'::character varying | extended | |
dropped_has_existingxxxxxxx | character varying(10) |
| extended | |
Indexes:
"setupinfo_pkey" PRIMARY KEY, btree (id)
"setupinfo_clientid_key" UNIQUE CONSTRAINT, btree (clientid)
Foreign-key constraints:
"setupinfo_clientid_fkey" FOREIGN KEY (clientid) REFERENCES
control.client(id)
Has OIDs: no
db=#
On Thu, May 9, 2013 at 4:24 PM, Tom Lane <[email protected]> wrote:
> "Evan D. Hoffman" <[email protected]> writes:
> > Looks like your guess was correct:
>
> Could we see the full schema (eg psql \d+) for setupinfo?
>
> regards, tom lane
>
