| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Mount <petermount(at)maidstone(dot)gov(dot)uk> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [INTERFACES] RE: JDBC now needs updates for large objects |
| Date: | 2000-10-24 12:44:01 |
| Message-ID: | 4983.972391441@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
Peter Mount <petermount(at)maidstone(dot)gov(dot)uk> writes:
> Idea: As we have this type of query in more than one part of the source tree
> (ie: psql, jdbc, probably odbc), should we have a section in the
> documentation containing common queries, like: retrieving a list of tables,
> views etc?
That's a good thought. It'd be a useful practice to review such
standard queries from time to time anyway. For example, now that
outer joins work, a lot of psql's backslash-command queries could
be simplified (don't need the UNION ALL WITH SELECT NULL hack).
Anyone have time to work up a list?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2000-10-24 14:24:41 | Fallback behavior for "UNKNOWN" types -- proposed change |
| Previous Message | Peter Mount | 2000-10-24 12:43:16 | RE: [INTERFACES] RE: JDBC now needs updates for large objects |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Lang | 2000-10-24 14:03:28 | Re: Problem : ERRNOUS pg_hba.conf file |
| Previous Message | Peter Mount | 2000-10-24 12:43:16 | RE: [INTERFACES] RE: JDBC now needs updates for large objects |