Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> How do you mean "where"?
> I was more wondering where in the source tree to put and how to install
> it. I would suggest the following: I have a file information_schema.sql
> which contains the commands to create the information
Tom Lane writes:
> How do you mean "where"? The spec says it's gotta be called
> information_schema, no? What's left to decide?
I was more wondering where in the source tree to put and how to install
it. I would suggest the following: I have a file information_schema.sql
which contains the co
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Christopher Kings-Lynne writes:
>> We could do DESCRIBE commands as well. Also, what happened to the
>> INFORMATION_SCHEMA proposal? Wasn't Peter E doing something with that?
>> What happened to it?
> Ooops. Yeah, let's get this in. Where should I
Christopher Kings-Lynne writes:
> We could do DESCRIBE commands as well. Also, what happened to the
> INFORMATION_SCHEMA proposal? Wasn't Peter E doing something with that?
> What happened to it?
Ooops. Yeah, let's get this in. Where should I put it?
--
Peter Eisentraut [EMAIL PROTECTED]
> ... and that was already proposed for "show schemas" (namespaces).
>
> I'm inclined to think it's time to bite the bullet and go over to
> words rather than single characters to identify the \d target
> (viz, "\dschema", "\dcast", etc, presumably with unique abbreviations
> being allowed, as well
[ moved to hackers from pgsql-patches ]
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Peter wrote:
>> Christopher Kings-Lynne writes:
>>> \dc - list conversions [PATTERN]
>>> \dC - list casts
>>
>> What are we going to use for collations?
> \dn Is the only letter left in collations t
