Re: [DOCS] Terms.

2010-09-20 Thread Bruce Momjian
Robert Haas wrote:
> With respect to PQnfields() vs. PQftablecol(), I think the word
> "fields" is being used to refer to the columns of the result set, and
> the word "columns" to refer to the columns of tables on the server.
> So PQftablecol() is actually trying to tell you the number of the
> table column where a particular "field" in the results came from.
> This is sort of a subtle distinction, though, and the fact that
> "field" is being abbreviated to "f" in some but not all cases doesn't
> make it any more clear.  PQftablecol() is really supposed to mean
> "field-table-column" - i.e. look up the table column for this field.
> But the name is definitely less than totally self-documenting.

FYI, many of these function names date back to Berkeley.  Libpq is
called 'libpq' because of the original use of the QUEL query language,
i.e. lib Post-QUEL.  We have a proud backward-compatibility history with
this library.

-- 
  Bruce Momjian  http://momjian.us
  EnterpriseDB http://enterprisedb.com

  + It's impossible for everything to be true. +

-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs


Re: [DOCS] Terms.

2010-09-20 Thread Dmitriy Igrishin
Hey Bruce,

Its interesting indeed, because I always wanted to know why libpq
named "libpq". Thanks!
But I wrote not about libpq functions, I just wanted to say about
unnecessary (IMO) redundancy - the combinations of terms "backend server"
seems to me inaccuracy.

-- 
Regards,
Dmitriy