Search Postgresql Archives

Re: =?gb18030?b?SSBhZGRlZCBhIKHMIG9wZXJhdG9yLCB0aGUgc3Fy?==?gb18030?b?dCBmdW5jdGlvbiBpcyBzdGlsbCB1c2VkIGludGVy?==?gb18030?b?bmFsbHksIGJ1dCBub3cgdGhlcmUgaXMgYSBwcm9i?==?gb18030?b?bGVtLCBpdCBhZmZlY3RzIHRoZSA6PSBhbmQgLi4g?==?gb18030?b?b3BlcmF0b3JzIG9mIHRoZSBkYXRhYmFzZQ==?=

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"=?gb18030?B?ucKwwdChtv6hq7Ci4+U=?=" <2903807914@xxxxxx> writes:
> # Description of Requirement:
> 1¡¢select ¡Ì num1; function
> 2¡¢The value of num1 is required to be: [0,9223372036854775807]
> 3¡¢¡Ì The operation does not allow decimals

Looks suspiciously like a homework assignment.

> I have now developed this feature on the PostgreSQL 14.0 kernel! But it affects the original function of the database:
> #&nbsp;Affected place
> 1¡¢ := assignment operator
> 2¡¢ Operator in 1..10

Today's lesson is: read the comments on the code you're modifying.
Notably on gram.y's list of "non keyword" tokens:

 * Non-keyword token types.  These are hard-wired into the "flex" lexer.
 * They must be listed first so that their numeric codes do not depend on
 * the set of keywords.  PL/pgSQL depends on this so that it can share the
 * same lexer.  If you add/change tokens here, fix PL/pgSQL to match!

Since you didn't do that, PL/pgSQL is confused about the token codes
in use for DOT_DOT and so on.

			regards, tom lane






[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux