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

more improvements to release notes

From: Neil Conway <neilc(at)samurai(dot)com>
To: PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: more improvements to release notes
Date: 2003-10-22 06:24:03
Message-ID: 1066803843.374.76.camel@tokyo (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
This patch makes a bunch of improvements to the release notes. I only
modified release.sgml -- HISTORY will need to be regenerated.

I was able to remove almost all of the "Other uncategorized" release
note entries, but left a few that I wasn't sure what to do with. We
should remove this section, and move the remaining entries to other
sections if necessary.

I had a few questions on some of the entries:

What is the following release note entry supposed to mean? "FETCH 0"
doesn't "do nothing", it now fetches the current cursor row. Bruce,
could you clarify this please?

     * MOVE/FETCH 0 now does nothing; return value of MOVE/FETCH 1/0
       varies based on the current offset in the cursor

This entry is plainly wrong:

     * Cause FETCH 1 to return the current cursor row, or zero if at
       beginning/end of cursor, per SQL spec (Bruce)

FETCH 0 is what actually returns the current cursor row, and returning
"zero" when a row value is expected wouldn't make much sense. I've
changed it to just say:

     * Cause FETCH 0 to return the current cursor row, per SQL spec

If I've missed some of the intent of the original entry, let me know.

These two entries are duplicates, right?

     * Have SHOW DATESTYLE generate output similar to that used by SET
       DATESTYLE (Tom)
     * Change DATESTYLE to output its value in a more common format

I wasn't sure, so I didn't make this change in the patch.


Attachment: relnotes-improv-2.patch
Description: text/x-patch (24.0 KB)


pgsql-patches by date

Next:From: Christopher Kings-LynneDate: 2003-10-22 07:21:23
Subject: Timestamp docs weirdness
Previous:From: Tom LaneDate: 2003-10-22 02:49:47
Subject: Re: [HACKERS] obj_description problems?

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