Jim C. Nasby wrote:
>On Tue, Jun 06, 2006 at 07:43:59PM -0300, Marc G. Fournier wrote:
>
>
>>On Tue, 6 Jun 2006, Jim C. Nasby wrote:
>>
>>
>>
>>>On Tue, Jun 06, 2006 at 02:44:20PM -0700, Darcy Buskermolen wrote:
>>>
>>>
>>>>so the output of \df ??
>>>>
>>>>
>>>I tend to find the output of \df pretty useless unless you already know
>>>what the function you want is called.
>>>
>>>
>>The neat 'chart' that the programming dept at the University I worked at
>>had was a chart of system tables for Oracle, showing the
>>inter-relationships between them ... just to add my 2c worth ...
>>
>>
>
>There's actually a number of 'cheat sheets' that could be created.
>System tables (though having something like newsysviews would probably
>eliminate a lot of the need for that), system/stats views, function
>reference, pl* reference, interface API references, etc.
>
>
I am collecting all of your suggestions, and they are great! Perhaps we
could provide a significance to the Guide Project by following the lead
of several software study guides, which are 6 - 8 x 11 colored sheets
laminated, and folded into thirds (this size doesn't get lost in thrown
away mags). The engineering needs of programmers could be accomodated,
the marketing needs of postgresql could be accomodated, and the
promotional needs of profit-making companies who consistently support
postgresql could be accomodated. Any actual physical content you all
may have to share, please send to me via email at: mdean@sourceview.com,
or if a physical specimen, send to: Michael Dean, SourceView
Corporation, 716 Alhambra Ave., Martinez, CA 94553 USA. All materials
received will be treated as "creative commons" materials. Thanks
