Re: [BUGS] Bug in date_part()

2001-01-18 Thread phil
Thanks for the reply Tom Lane, and Tom Lockhart. On my 7.0.3: phil=# select '4/1/2001'::date::timestamp; ?column? 2001-03-31 23:00:00-08 (1 row) This was built from source downloaded from the primary FTP site link on www.postgresql.org. [cartret@Sti

[BUGS] Install/regression test instructions don't work.

2001-01-18 Thread Koch, Kevin
Downloaded V7.0.3 from latest area. Followed build instructions on my Alpha Linux box. Regression test instructions do not work as postmaster (or something similarly named) isn't running. If this is part of Postgresql, you need to say how to start it. If its not part of postgresql, you need to

Re: [BUGS] pgsql-loophole-request@postgresql.org does not exist

2001-01-18 Thread The Hermit Hacker
long ago gone ... if you want to get on a list to post to, without being swamped with email, send a 'subscribe-nomail' to the -request address for the list ... especially great for those using news to post to the lists :) On Wed, 17 Jan 2001, Jason Schroeder wrote: > http://www.postgresql.org/

[BUGS] minor fault report

2001-01-18 Thread Bert de Jong
Hi, when I ./pg_dump -?, the text that's shown ends: "...if no database name is not supplied..." bye, Bert

Re: [BUGS] Re: Bug in date_part()

2001-01-18 Thread phil
Ah, I think I understand the trouble now. It's good it's fixed for the next release. And, as predicted, I'm running in a DST zone (/etc/localtime -> ../usr/share/zoneinfo/US/Pacific) Thanks for the quick diagnosis! Phil On Wed, Jan 17, 2001 at 09:07:34PM -0500, Tom Lane wrote: > Thomas Lock

[BUGS] ascii() picks up sign bit past CHAR value 127

2001-01-18 Thread pgsql-bugs
ascii() returns negative ASCII values? ([EMAIL PROTECTED]) reports a bug with a severity of 4 The lower the number the more severe it is. Short Description ascii() picks up sign bit past CHAR value 127 Long Description The lack of an UNISIGNED INT1 attribute type forces those of us who need a

Re: [BUGS] ascii() picks up sign bit past CHAR value 127

2001-01-18 Thread Tom Lane
[EMAIL PROTECTED] writes: > The lack of an UNISIGNED INT1 attribute type forces those of us who > need a positive numeric byte type to use CHAR. The ascii() function > ostensibly returns the numeric ASCII value of the corresponding CHAR > attribute value - but once you get beyond the 0-127 ACCII