Skip site navigation (1) Skip section navigation (2)

Re: [REVIEW] Patch for cursor calling with named parameters

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <yebhavinga(at)gmail(dot)com>,<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [REVIEW] Patch for cursor calling with named parameters
Date: 2011-12-03 20:53:43
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
The patch is in context format, includes docs and additional
regression tests, applies cleanly, passes "world" regression tests.
The parser changes don't cause any "backing up".
Discussion on the list seems to have reached a consensus that this
patch implements a useful feature.  A previous version was reviewed.
This version attempts to respond to points previously raised.
Overall, it looked good, but there were a few things I would like Yeb
to address before mark it is marked ready for committer.  I don't
think any of these will take long.
(1)  Doc changes:
  (a) These contain some unnecessary whitespace changes which make it
      harder to see exactly what changed.
  (b) There's one point where "cursors" should be possessive
  (c) I think it would be less confusing to be consistent about
      mentioning "positional" and "named" in the same order each
      time. Mixing it up like that is harder to read, at least for
(2)  The error for mixing positional and named parameters should be
moved up.  That seems more important than "too many arguments" or
"provided multiple times" if both are true.
(3)  The "-- END ADDITIONAL TESTS" comment shouldn't be added to the
regression tests.
The way this parses out the named parameters and then builds the
positional list, with some code from read_sql_construct() repeated in
read_cursor_args() seems a little bit clumsy to me, but I couldn't
think of a better way to do it.


pgsql-hackers by date

Next:From: Peter EisentrautDate: 2011-12-03 21:46:21
Subject: missing rename support
Previous:From: Michael MeskesDate: 2011-12-03 20:49:25
Subject: Re: SQLDA fix for ECPG

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group