Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commite256baf

Browse files
committed
Eliminate a gratuitously different wording of the 'cannot use aggregate function in check constraint' error message.
1 parent1d895f4 commite256baf

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎src/backend/commands/typecmds.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
*
99
*
1010
* IDENTIFICATION
11-
* $PostgreSQL: pgsql/src/backend/commands/typecmds.c,v 1.90 2006/04/05 22:11:55 tgl Exp $
11+
* $PostgreSQL: pgsql/src/backend/commands/typecmds.c,v 1.91 2006/06/21 18:09:53 tgl Exp $
1212
*
1313
* DESCRIPTION
1414
* The "DefineFoo" routines take the parse tree and pick out the
@@ -1841,7 +1841,7 @@ domainAddConstraint(Oid domainOid, Oid domainNamespace, Oid baseTypeOid,
18411841
if (pstate->p_hasAggs)
18421842
ereport(ERROR,
18431843
(errcode(ERRCODE_GROUPING_ERROR),
1844-
errmsg("cannot use aggregate in check constraint")));
1844+
errmsg("cannot use aggregatefunctionin check constraint")));
18451845

18461846
/*
18471847
* Convert to string form for storage.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp