Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Facebook
Downloads
Home
>
mailing lists
table column vs. out param [1:0] - Mailing list pgsql-general
From
Kristo Kaiv
Subject
table column vs. out param [1:0]
Date
August 23, 2007
07:56:51
Msg-id
5177DE35-7DAD-4DAF-B314-242DAA2B15D1@skype.net
Whole thread
Raw
Responses
Re: table column vs. out param [1:0]
(Kristo Kaiv <kristo.kaiv@skype.net>)
List
pgsql-general
Tree view
I am trying to implement the new out parameters in functions and stumbled upon a problem.
There is an internal requirement for our databases that every function call always returns 2 params status & status_text.
The problem now is that plpgsql selects the out params themselves into out params instead of function call results that i need there.
If this is the expected behavior of out params it makes using out params a bit complicated if some table attributes
happen to have the same name as out params. How can i overcome this situation? I can understand function variables having precedence
over column names as you can freely rename them but out params is a different situation.
snippet from code
-[cut]--
out status int, -- 200
out status_text text -- OK
) AS $$
BEGIN
-[cut]--
SELECT status, status_text
FROM service._simple_add(
i_key_user
,i_key_service
,i_action
,i_subscr_len)
INTO status, status_text;
-[cut]-
Kristo Kaiv
http://kaiv.wordpress.com
(PostgreSQL blog)
pgsql-general
by date:
Previous
From:
"Patrick Lindeman"
Date:
23 August 2007, 07:51:26
Subject:
Re: CPU load high
Next
From:
"Max Zorloff"
Date:
23 August 2007, 08:05:59
Subject:
Re: CPU load high
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
I confirm that I have read and accepted PostgresPro’s
Privacy Policy
.
I agree to get Postgres Pro discount offers and other marketing communications.
✖
×
×
Everywhere
Documentation
Mailing list
List:
all lists
pgsql-general
pgsql-hackers
buildfarm-members
pgadmin-hackers
pgadmin-support
pgsql-admin
pgsql-advocacy
pgsql-announce
pgsql-benchmarks
pgsql-bugs
pgsql-chat
pgsql-cluster-hackers
pgsql-committers
pgsql-cygwin
pgsql-docs
pgsql-hackers-pitr
pgsql-hackers-win32
pgsql-interfaces
pgsql-jdbc
pgsql-jobs
pgsql-novice
pgsql-odbc
pgsql-patches
pgsql-performance
pgsql-php
pgsql-pkg-debian
pgsql-pkg-yum
pgsql-ports
pgsql-rrreviewers
pgsql-ru-general
pgsql-sql
pgsql-students
pgsql-testers
pgsql-translators
pgsql-www
psycopg
Period
anytime
within last day
within last week
within last month
within last 6 months
within last year
Sort by
date
reverse date
rank
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
By continuing to browse this website, you agree to the use of cookies. Go to
Privacy Policy
.
I accept cookies