Re: Some problems with (my?) PlSQL

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Rui Pacheco <rep(at)devdomain(dot)com>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Some problems with (my?) PlSQL
Date: 2002-06-04 22:18:19
Message-ID: 20020604151623.Y6858-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Tue, 4 Jun 2002, Rui Pacheco wrote:

> BEGIN
>
> UPDATE TS_USERS SET
> LOGIN = strLogin, EMAIL = strEmail, TITLE = strTitle, FIRST_NAME =
> strFirstName,
> LAST_NAME = strLastName, DATE_CREATION = TIMESTAMP (strDateCreation),
> DATE_LAST_ACCESS = TIMESTAMP (strDateLastAccess), ACC_LOCKED =
> strAccLocked,
> ACC_DISABLED = strAccDisabled, PASSWD_CHALLENGE = strPasswdChallenge,
> PASSWD_CHALLENGE_RESPONSE = strPasswdChallengeResponse
> WHERE ID = intId;
>
> RETURN 1;
> END;
> ' LANGUAGE 'plpgsql';
> -------
>
> While not reaching the limit of arguments, this function, when called, gives
> me this error:
>
> Query error [SELECT devUsersUpdate ('1', 'root', '', 'root(at)somehost(dot)com',
> '', 'Super', 'User', '0001-01-01', '0001-01-01', 'N', 'N', '', '')]: ERROR:
> parser: parse error at or near "$6"

Wierd that it would say $6. You might be getting bitten by the changes to
timestamp. Maybe using "timestamp"(strDateCreation) and
"timestamp"(strDateLastAccess) would make it work.

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Haddon 2002-06-04 23:04:03 alter column - NOT NULL
Previous Message Rui Pacheco 2002-06-04 22:02:01 Some problems with (my?) PlSQL