From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | issue: record or row variable cannot be part of multiple-item INTO list |
Date: | 2017-05-13 19:24:36 |
Message-ID: | CAFj8pRB76FE2MVxJYPc1RvXmsf2upoTgoPCC9GsvSAssCM2APQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
I am working on migration large Oracle application to Postgres. When I
started migration procedures with OUT parameters I found following limit
"record or row variable cannot be part of multiple-item INTO list"
I checked code and it looks so this limit is not necessary for ROW types
(what is enough for migration from Oracle, where REC is not available).
Do you think so this limit is necessary for ROW types?
@@ -3368,19 +3368,7 @@ read_into_target(PLpgSQL_rec **rec, PLpgSQL_row
**row, bool *strict)
switch (tok)
{
case T_DATUM:
- if (yylval.wdatum.datum->dtype == PLPGSQL_DTYPE_ROW)
- {
- check_assignable(yylval.wdatum.datum, yylloc);
- *row = (PLpgSQL_row *) yylval.wdatum.datum;
-
- if ((tok = yylex()) == ',')
- ereport(ERROR,
- (errcode(ERRCODE_SYNTAX_ERROR),
- errmsg("record or row variable cannot be part
of multiple-item INTO list"),
- parser_errposition(yylloc)));
- plpgsql_push_back_token(tok);
- }
- else if (yylval.wdatum.datum->dtype == PLPGSQL_DTYPE_REC)
Regards
Pavel
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Dolgov | 2017-05-13 19:42:32 | Re: logical decoding of two-phase transactions |
Previous Message | Tom Lane | 2017-05-13 19:18:53 | Re: Valgrind & tests for `numeric` |