cool, thanks
yes, i was slack reading th docs
m
Jan Wieck wrote:
>
> Murray Hobbs wrote:
> >
> > i neglected to show it properly
> >
> > have tables A, B, C, D PLUS a few others
> >
> > A <- B
> >
> > F
> > |
> > v
> > A <- C <- D
> > ^
> > |
> > E
> >
> > i want
Murray Hobbs wrote:
>
> i neglected to show it properly
>
> have tables A, B, C, D PLUS a few others
>
> A <- B
>
> F
> |
> v
> A <- C <- D
> ^
> |
> E
>
> i want to delete from C and cascade any delete to E or F but not if
> there are records in D
>
> what i have don
On Thu, 23 Aug 2001, Tom Lane wrote:
> "Josh Berkus" <[EMAIL PROTECTED]> writes:
> >> What's the correct syntax to return two VARCHAR(255)?
>
> > There isn't one. At this time, functions cannot return arrays.
>
> Well, they *can*, it's just that there's no syntax to support
> constructing an a
i neglected to show it properly
have tables A, B, C, D PLUS a few others
A <- B
F
|
v
A <- C <- D
^
|
E
i want to delete from C and cascade any delete to E or F but not if
there are records in D
what i have done is to have ON DELETE CASCADE on C's primary
Other SQL servers have the concept of stored procedures having different
permissions.
For instance a procedure that can update a table.
Since a web site typically connects as the webuser (or equiv postgres
user), I do not want to offer update to the webuser.
The way I have done this elsewhere i
"Josh Berkus" <[EMAIL PROTECTED]> writes:
>> What's the correct syntax to return two VARCHAR(255)?
> There isn't one. At this time, functions cannot return arrays.
Well, they *can*, it's just that there's no syntax to support
constructing an array value in SQL or plpgsql languages.
I know that
Ciao Francesco:
> What's the correct syntax to return two VARCHAR(255)?
There isn't one. At this time, functions cannot return arrays. Look
for a fix to this limitation with version 7.2 or later.
Jan Wieck and others have been working to extend functions so that they
may manipulate and retur
I want a function to return an array of two VARCHAR(255).
This works, but does not return VARCHAR(255):
CREATE FUNCTION ins_div(CHAR(8))
RETURNS _varchar
AS '...'
LANGUAGE 'plpgsql';
These don't work:
CREATE FUNCTION ins_div(CHAR(8))
RETURNS _varchar(255)
AS '...'
LANGUAGE 'plpgsql';
CREATE FUN
Murray Hobbs wrote:
>
> here's my problem
>
> i have tables A, B, C, D
>
> A <- B
> A <- C <- D
>
> i want to maintain integrity so that if A is deleted from then so is
> anything referencing from B and C - no problem ON DELETE CASCADE
>
> but if there are any D's that point back to A (through com
