Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > My idea on this after chat with Dave was to add a GUC option that puts
> > the schema.table.column name as the default column label, rather than
> > just the column name.
> And will you quotify things so that names containing dots, spaces, etc
> are unambiguous?
> I think the above is a very poor substitute for doing it properly,
> namely returning the values in separate fields.  We should not allow
> ourselves to get lured into a dead end just because we can do it without
> obviously breaking the protocol.  (I would argue that this breaks the
> protocol anyway, though.)

I don't see how it is worth modifying the client or protocol unless we
have more demand for it.  I would quote the labels, yes.

> > I am not overly excited
> > about doing this at the protocol level unless there is major need for it.
> I'm not excited about doing it at all, unless we do it right.  We can
> already have half-baked solutions on the client side ;-)

It is easy on the server, quite hard on the client.

  Bruce Momjian                        |
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Reply via email to