From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | ivan <iv(at)psycho(dot)pl> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: sugsestions |
Date: | 2003-07-09 13:26:28 |
Message-ID: | 1057704413.46100.58.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2003-07-08 at 21:31, ivan wrote:
> What do you think about :
>
> 1. OPTION RETURNS NULL ON NULL INPUT (when function is created) change to
> RETURNS <val> ON NULL INPUT .... ???
I personally think this should be up to the specific function to
capture. This way it could be a complex result.
> 2. CREATE TYPE .. with INHERITS (..) like in CREATE TABLE
> but type should be normaly with including base type
> create type A AS (A INT,B INT);
> and
> create type B AS (C INT, D INT) INHERITS( A ); ==
> create type B AS (A INT, B INT, C INT, D INT );
> can be ??
I like this. The equivalent table syntax for absorbing table structure
into another table is LIKE:
CREATE TABLE othertable (acol integer);
CREATE TABLE a (col integer, LIKE othertable, anothercol integer);
I could see:
CREATE TYPE a AS (a integer, b integer);
CREATE TYPE b AS (LIKE a, c integer, d integer);
> 5. What do you think about crontab in postgres database , like pg_crontab
> ?
This has been debated several times. Each time it has ended with
standard cron being the best solution for cron.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-07-09 15:35:37 | Re: CREATE DATABASE command in Extended Query mode of 3.0 |
Previous Message | Carlos Guzman Alvarez | 2003-07-09 12:05:18 | Transaction handling in extended query mode and Sync message issues |