Обсуждение: 7.2 Beta2 bug report

The parser seems to have changed from 7.1.3->7.2B2 in a bad way:
 test=# create table test(timestamp timestamp); ERROR:  parser: parse error at or near "timestamp"

Don't-ever-say-I-didn't-test-B2,
-Kevin

PS:  CC me on the results, and let me know if there is a better place to    submit bugs.  There didn't seem to be
anythingobvious on the developer    site.
 

--
Kevin Jacobs
The OPAL Group - Enterprise Systems Architect
Voice: (216) 986-0710 x 19         E-mail: jacobs@theopalgroup.com
Fax:   (216) 986-0714              WWW:    http://www.theopalgroup.com

On Wed, Nov 07, 2001 at 05:39:27PM -0500, Kevin Jacobs wrote:
> The parser seems to have changed from 7.1.3->7.2B2 in a bad way:
> 
>   test=# create table test(timestamp timestamp);
>   ERROR:  parser: parse error at or near "timestamp"
> 
> Don't-ever-say-I-didn't-test-B2,

(or even from 7.2devel -> 7.2b2) however

test=# create table test("timestamp" timestamp);
CREATE

=> I presume that timestamp has become reserved whereas before it wasn't?

Patrick

Kevin Jacobs <jacobs@penguin.theopalgroup.com> writes:
> I'm not very familiar with the grammar, but it seems strange that this works
> when timestamp does not:

>    test=# create table test (date date);

Type "date" hasn't got all those gnarly SQL92-isms that we support now:
TIMESTAMPTIMESTAMP(precision)TIMESTAMP WITH TIME ZONETIMESTAMP(precision) WITH TIME ZONETIMESTAMP WITHOUT TIME
ZONETIMESTAMP(precision)WITHOUT TIME ZONE
 

However, I'm wondering if something could be done by not having an
explicit production for the first of these, only the other ones.
Off to experiment with bison ...
        regards, tom lane

Kevin Jacobs <jacobs@penguin.theopalgroup.com> writes:
> The parser seems to have changed from 7.1.3->7.2B2 in a bad way:
>   test=# create table test(timestamp timestamp);
>   ERROR:  parser: parse error at or near "timestamp"

Unfortunately, this isn't a bug.

Unless we can figure out some way to accept SQL92 timestamp type
declarations without requiring TIMESTAMP to be a reserved word.
Hmm...
        regards, tom lane

On Wed, 7 Nov 2001, Kevin Jacobs wrote:

> The parser seems to have changed from 7.1.3->7.2B2 in a bad way:
> 
>   test=# create table test(timestamp timestamp);
>   ERROR:  parser: parse error at or near "timestamp"

I believe timestamp is now a reserved word. To name a column timestamp
you must double-quote it - during creation and anytime you want to use
it later - as in a query etc.


Cheers,
Rod
--                      Let Accuracy Triumph Over Victory
                                                      Zetetic Institute
     "David's Sling"                                                        Marc Stiegler
 

Timestamp is a reserved word.  You are a naughty person for using it
:).  However, I think that you will find that:

CREATE TABLE test ("timestamp" timestamp);

Works just fine.

Jason

Kevin Jacobs <jacobs@penguin.theopalgroup.com> writes:

> The parser seems to have changed from 7.1.3->7.2B2 in a bad way:
> 
>   test=# create table test(timestamp timestamp);
>   ERROR:  parser: parse error at or near "timestamp"
> 
> Don't-ever-say-I-didn't-test-B2,
> -Kevin
> 
> PS:  CC me on the results, and let me know if there is a better place to
>      submit bugs.  There didn't seem to be anything obvious on the developer
>      site.
> 
> --
> Kevin Jacobs
> The OPAL Group - Enterprise Systems Architect
> Voice: (216) 986-0710 x 19         E-mail: jacobs@theopalgroup.com
> Fax:   (216) 986-0714              WWW:    http://www.theopalgroup.com
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

On Thu, 8 Nov 2001, Tom Lane wrote:
> Kevin Jacobs <jacobs@penguin.theopalgroup.com> writes:
> > The parser seems to have changed from 7.1.3->7.2B2 in a bad way:
> >   test=# create table test(timestamp timestamp);
> >   ERROR:  parser: parse error at or near "timestamp"
>
> Unfortunately, this isn't a bug.
>
> Unless we can figure out some way to accept SQL92 timestamp type
> declarations without requiring TIMESTAMP to be a reserved word.
> Hmm...

I'm not very familiar with the grammar, but it seems strange that this works
when timestamp does not:
  test=# create table test (date date);

-Kevin

--
Kevin Jacobs
The OPAL Group - Enterprise Systems Architect
Voice: (216) 986-0710 x 19         E-mail: jacobs@theopalgroup.com
Fax:   (216) 986-0714              WWW:    http://www.theopalgroup.com