At 05:47 PM 11/8/00 -0600, Luis =?UNKNOWN?Q?Maga=F1a?= wrote:
>insert into employee(title,first_name,start_date,charge) values('Mr.
X','Smith',date(now()),'None');
>insert into employee(title,first_name,start_date,charge) values('Mr.
Y','Smith',date(now()),'None');
>insert into employee(title,fir
That would be an extreamly good reason then. I suppose I've fallen into
the 'other' standard :(
Tom Lane wrote:
>
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > I believe that the coalesce function can
> > get you out of this... Speaking of which, why isn't it called NVL()?
>
> Because the SQL9
Rod Taylor <[EMAIL PROTECTED]> writes:
> I believe that the coalesce function can
> get you out of this... Speaking of which, why isn't it called NVL()?
Because the SQL92 standard calls it coalesce.
regards, tom lane
Luis Magaña wrote:
>
> Hi:
>
> Have this curious situation and would like some help from you:
>
> Create an employee table:
>
> CREATE TABLE employee(
>id_employee SERIAL PRIMARY KEY,
>sex CHAR(1) DEFAULT 'm' CHECK(sex = 'f' OR sex = 'm'),
>start_date DATE NOT NULL,
>charge V
Hi:
Have this curious situation and would like some help from you:
Create an employee table:
CREATE TABLE employee(
id_employee SERIAL PRIMARY KEY,
sex CHAR(1) DEFAULT 'm' CHECK(sex = 'f' OR sex = 'm'),
start_date DATE NOT NULL,
charge VARCHAR(50) NOT NULL,
last_name VARCHAR(50
