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
Get / Set Composite Type Fields within triggers - Mailing list pgsql-general
From
Martin Durao
Subject
Get / Set Composite Type Fields within triggers
Date
June 24, 2013
08:00:23
Msg-id
CAF+QOjg72k+PkmoS8YGOJG3bH4xkrtivW8RBOVedpXfbgyJ=6A@mail.gmail.com
Whole thread
Raw
Responses
Re: Get / Set Composite Type Fields within triggers
List
pgsql-general
Tree view
Hi
This is my first question, so, forgive me if it's a newby issue but I couldn't find an answer googling.
I have a simple composite type
CREATE TYPE info_base AS
(by text,
at timestamp without time zone);
I want to use it as the data type of created, modified and deleted fields. I already know hot to index, update and select a sub-field like
CREATE INDEX ix_created_by ON xxx.yyy ((created).by);
UPDATE xxx.yyy SET
created.by
= 'user';
select * from xxx.yyy where (created).by = 'that user';
My problem is inside triggers: How can I set or get type field values for NEW or OLD? (I need it to check users permissions at row level, etc.)
I tried NEW.((created).by), NEW.(
created.by
),
NEW.created.by
and nothing works...
Could you help me please?
Thanks in advance.
Martin
pgsql-general
by date:
Previous
From:
Tatsuo Ishii
Date:
24 June 2013, 07:25:51
Subject:
postgres_fdw changes schema search path
Next
From:
Albe Laurenz
Date:
24 June 2013, 08:19:59
Subject:
Re: File size consideration of file_fdw in PostgreSQL
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
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