Re: [BUGS] Dates and year 2000
Just discovered that column::date works fine but to_date(column, 'DD.MM.YY') causes the problem. I was trying to write portable SQL, but never mind! Andy ""Andy Marden"" <[EMAIL PROTECTED]> wrote in message 007301c1baad$b60d7b90$010a@marden1">news:007301c1baad$b60d7b90$010a@marden1... > Do we have a workaround for 7.1.3? I don't really want to risk > an upgrade at this stage in the system > > Cheers > > Andy > - Original Message - > From: "Tom Lane" <[EMAIL PROTECTED]> > To: "Andy Marden" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Wednesday, February 20, 2002 11:21 PM > Subject: Re: [BUGS] Dates and year 2000 > > > > "Andy Marden" <[EMAIL PROTECTED]> writes: > > > Is this a bug? > > > > Yes. It's fixed in 7.2 ... > > > > regards, tom lane > > > > > ---(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] Full bug list
Is there a repository on the web somewhere of all the bugs found, versions they are found against and what theire status is? ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] Trying Cygwin version of PostgreSQL
Great! But where is the documentation on doing this stuff? I'd like to try. --- Tom Lane <[EMAIL PROTECTED]> wrote: > Peter <[EMAIL PROTECTED]> writes: > > I resorted to trial and error. Initdb hangs when > "Creating template1 > > database" so there must be a step missing. > > I think you forgot to run the cygipc daemon. > > regards, tom lane > > ---(end of > broadcast)--- > TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] Dates and year 2000
> Just discovered that column::date works fine but to_date(column, 'DD.MM.YY') > causes the problem. I was trying to write portable SQL, but never mind! Portable (as in SQL9x) would be cast(column as date) which is also accepted by PostgreSQL... - Thomas ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] [GENERAL] schema error upgrading from 7.1 to 7.2
> "TL" == Tom Lane <[EMAIL PROTECTED]> writes: TL> HISTORY says, under "Migration to version 7.2": TL> * The date/time value 'current' is no longer available. You TL>will need to rewrite your applications. I see now. Thanks. I didn't make the connection between "current" and "CURRENT_DATE". ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[BUGS]
i have installed postgreSql Server on windows2000 but on startup it gives a message Version expired Pls help Hardeep Singh BhatiaSoftware AnalystNeel Software Pvt LtdUnit 17, Electronics Sadan IIIMIDC, Bhosari, Pune 411026Ph: +(91)-(20)-712 9421 E-Mail: [EMAIL PROTECTED]
[BUGS] (plpgsql) DECLARE foo NUMERIC(5,2): syntax error at "("
PL/pgSQL docs say "PL/pgSQL variables can have any SQL datatype".
but when i try:
CREATE FUNCTION foo() RETURNS NUMERIC(5,2) AS '
DECLARE
bar NUMERIC(5,2);
BEGIN
bar := 123.45;
return bar;
END;
' LANGUAGE 'plpgsql';
then "select foo()" gives:
NOTICE: plpgsql: ERROR during compile of foo near line 2
ERROR: parse error at or near "("
declaring bar as "FLOAT8" (for example) works as expected.
from a quick look at plpgsql/src/gram.y, the decl_dtypename rule
only allows type modifiers (decl_attypmod) on CHAR, VARCHAR or BPCHAR.
scan.l doesn't even recognise NUMERIC or DECIMAL as keywords.
(debian postgresql 7.1.3-6 package on Linux/Intel)
--
- Gus
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] (plpgsql) DECLARE foo NUMERIC(5,2): syntax error at "("
Angus Lees <[EMAIL PROTECTED]> writes: > from a quick look at plpgsql/src/gram.y, the decl_dtypename rule > only allows type modifiers (decl_attypmod) on CHAR, VARCHAR or BPCHAR. This is fixed in 7.2. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] Full bug list
Hi Andy, Thats the reason which techdocs.postgresql.org started for, but since it's grown to encompass so many things, that section hasn't been updated in ages. :-( Perhaps its time to look at a better way of keeping it updated? :-) Regards and best wishes, Justin Clift On Thursday 21 February 2002 20:32, Andy Marden wrote: > Is there a repository on the web somewhere of all the bugs found, versions > they are found against and what theire status is? > > > > ---(end of broadcast)--- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED]) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] Trying Cygwin version of PostgreSQL
Hi Paul, You might like to try the very good installation guide for PostgreSQL on Windows at : http://www.ejip.net/faq/postgresql_win_setup_faq.jsp Added a link to it from the techdocs.postgresql.org website earlier today too. :-) Regards and best wishes, Justin Clift On Thursday 21 February 2002 23:37, Paul Rowland wrote: > Great! But where is the documentation on doing this > stuff? I'd like to try. > > --- Tom Lane <[EMAIL PROTECTED]> wrote: > > Peter <[EMAIL PROTECTED]> writes: > > > I resorted to trial and error. Initdb hangs when > > > > "Creating template1 > > > > > database" so there must be a step missing. > > > > I think you forgot to run the cygipc daemon. > > > > regards, tom lane > > > > ---(end of > > broadcast)--- > > TIP 1: subscribe and unsubscribe commands go to > > [EMAIL PROTECTED] > > > __ > Do You Yahoo!? > Yahoo! Sports - Coverage of the 2002 Olympic Games > http://sports.yahoo.com > > ---(end of broadcast)--- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] PostgresSQL 7.1.3 not parsing SELECT portion of SQL correctly
Is this a TODO item? Seems so. Comments? --- Tom Lane wrote: > "Mark Jeacocke" <[EMAIL PROTECTED]> writes: > > select DISTINCT TABLEID, '' AS ALIAS from TABLE; :FAILS > > We get this type of complaint regularly. Perhaps DISTINCT should > resolve unknown-type inputs to "text", much as we do with CASE > and UNION constructs when we see an untyped literal. Thoughts? > > regards, tom lane > > PS: in the meantime, Mark, try casting the literal to text. > > ---(end of broadcast)--- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] Bug #599: ecpg does not parse correctly define and struct in the same file
BAZIN Nicolas ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
ecpg does not parse correctly define and struct in the same file
Long Description
The following example does not get pre-processed:
EXEC SQL ifndef COMMERCANT;
EXEC SQL define COMMERCANT;
EXEC SQL define CMR_CODE 10;
EXEC SQL define CMR_NUMCMR 7;
EXEC SQL define CMR_NOM 32;
EXEC SQL define CMR_ABRVNOM 15;
EXEC SQL define CMR_ADRS132;
EXEC SQL define CMR_ABRVADRS 15;
EXEC SQL define CMR_ADRS232;
EXEC SQL define CMR_TEL 15;
EXEC SQL define CMR_CODACTIVITE 4;
EXEC SQL define CMR_CODZONE 2;
EXEC SQL define CMR_CODBQE 5;
EXEC SQL define CMR_NUMBADGE 15;
EXEC SQL define CMR_DATDEBUT 10;
EXEC SQL define CMR_DATFIN 10;
EXEC SQL define CMR_TEST 1;
EXEC SQL define CMR_PLFCODE 1;
EXEC SQL BEGIN DECLARE SECTION;
struct tcommercant
{
char cmr_code [CMR_CODE+1];
char cmr_numcmr[CMR_NUMCMR+1];
char cmr_nom [CMR_NOM+1];
char cmr_abrvnom [CMR_ABRVNOM+1];
char cmr_adrs1 [CMR_ADRS1+1];
char cmr_abrvadrs [CMR_ABRVADRS+1];
char cmr_adrs2 [CMR_ADRS2+1];
char cmr_tel [CMR_TEL+1];
char cmr_codactivite [CMR_CODACTIVITE+1];
char cmr_codzone [CMR_CODZONE+1];
char cmr_codbqe[CMR_CODBQE+1];
char cmr_numbadge [CMR_NUMBADGE+1];
char cmr_datdebut [CMR_DATDEBUT+1];
char cmr_datfin[CMR_DATFIN+1];
char cmr_test [CMR_TEST+1];
char cmr_plfcode [CMR_PLFCODE+1];
};
EXEC SQL END DECLARE SECTION;
EXEC SQL endif;
The pre-processor stops at the first char declaration after struct. This can be
reproduced in test1.pgc if an EXEC SQL ifndef COMMERCANT;EXEC SQL define COMMERCANT;
...;EXEC SQL endif; is added between the struct declaration.
Sample Code
No file was uploaded with this report
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] Bug #597: ResultSet.next() throws NullPointerException
This has been saved for the 7.3 release:
http://candle.pha.pa.us/cgi-bin/pgpatches2
---
[EMAIL PROTECTED] wrote:
> Craig Brown ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> ResultSet.next() throws NullPointerException
>
> Long Description
> When invoking the next() method on a ResultSet that has been closed a
>NullPointerException is thrown. Ideally, an SQLException stating that the ResultSet
>has been closed should be thrown.
>
> This bug affects several other methods within the jdbc2/ResultSet class.
>
> Sample Code
> This patch fixes the above described problem.
>
> *** ./src/interfaces/jdbc/org/postgresql/errors.properties.orig Tue Feb 19 17:54:02
>2002
> --- ./src/interfaces/jdbc/org/postgresql/errors.properties Tue Feb 19 17:49:55
>2002
> ***
> *** 54,59
> --- 54,60
> postgresql.res.badshort:Bad Short {0}
> postgresql.res.badtime:Bad Time {0}
> postgresql.res.badtimestamp:Bad Timestamp Format at {0} in {1}
> + postgresql.res.closed:The ResultSet has been closed.
> postgresql.res.colname:The column name {0} not found.
> postgresql.res.colrange:The column index is out of range.
> postgresql.serial.interface:You cannot serialize an interface.
> *** ./src/interfaces/jdbc/org/postgresql/jdbc2/ResultSet.java.orig Tue Feb 19
>17:53:46 2002
> --- ./src/interfaces/jdbc/org/postgresql/jdbc2/ResultSet.java Tue Feb 19 17:50:12
>2002
> ***
> *** 110,115
> --- 110,118
> */
> public boolean next() throws SQLException
> {
> + if (rows == null)
> + throw new PSQLException("postgresql.res.closed");
> +
> if (++current_row >= rows.size())
> return false;
> this_row = (byte [][])rows.elementAt(current_row);
> ***
> *** 702,707
> --- 705,713
> */
> public java.sql.ResultSetMetaData getMetaData() throws SQLException
> {
> + if (rows == null)
> + throw new PSQLException("postgresql.res.closed");
> +
> return new ResultSetMetaData(rows, fields);
> }
>
> ***
> *** 828,833
> --- 834,841
> // index is 1-based, but internally we use 0-based indices
> int internalIndex;
>
> + if (rows == null)
> + throw new PSQLException("postgresql.res.closed");
> if (index == 0)
> throw new SQLException("Cannot move to index of 0");
>
> ***
> *** 866,871
> --- 874,882
>
> public void afterLast() throws SQLException
> {
> + if (rows == null)
> + throw new PSQLException("postgresql.res.closed");
> +
> final int rows_size = rows.size();
> if (rows_size > 0)
> current_row = rows_size;
> ***
> *** 873,878
> --- 884,892
>
> public void beforeFirst() throws SQLException
> {
> + if (rows == null)
> + throw new PSQLException("postgresql.res.closed");
> +
> if (rows.size() > 0)
> current_row = -1;
> }
> ***
> *** 891,896
> --- 905,913
>
> public boolean first() throws SQLException
> {
> + if (rows == null)
> + throw new PSQLException("postgresql.res.closed");
> +
> if (rows.size() <= 0)
> return false;
> current_row = 0;
> ***
> *** 1035,1040
> --- 1052,1060
>
> public int getFetchSize() throws SQLException
> {
> + if (rows == null)
> + throw new PSQLException("postgresql.res.closed");
> +
> // new in 7.1: In this implementation we return the entire result
>set, so
> // here return the number of rows we have. Sub-classes can return a
>proper
> // value
> ***
> *** 1078,1083
> --- 1098,1106
>
> public int getRow() throws SQLException
> {
> + if (rows == null)
> + throw new PSQLException("postgresql.res.closed");
> +
> final int rows_size = rows.size();
>
> if (current_row < 0 || current_row >= rows_size)
> ***
> *** 1108,1135
> --- 1131,1173
>
> public boolean isAfterLast() throws SQLException
> {
> + if (rows == null)
> + throw new PSQLException("postgresql.res.closed");
> +
> final int rows_size = rows.size();
> return (curr
Re: [BUGS] Trying Cygwin version of PostgreSQL again
Peter wrote: > > Justin Clift suggested: > http://www.ejip.net/faq/postgresql_win_setup_faq.jsp > I started from scratch following the page and adapting it where it is > out of date. I reached the stage of starting postmaster and receiving > the message: > DEBUG: pq_recvbuf: unexpected EOF on client connection > DEBUG: incomplete startup packet Aww Rats. I'll try it tonight and see how it goes for me. Did you use PostgreSQL 7.2 or 7.1.3? :-) Regards and best wishes, Justin Clift > Peter -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
