| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "frank_lupo" <frank_lupo(at)email(dot)it> |
| Cc: | "pgadmin-hackers" <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: rule on view in pgschema |
| Date: | 2003-04-08 10:18:31 |
| Message-ID: | 03AF4E498C591348A42FC93DEA9661B8259F2B@mail.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
> -----Original Message-----
> From: frank_lupo [mailto:frank_lupo(at)email(dot)it]
> Sent: 08 April 2003 11:08
> To: Dave Page
> Cc: pgadmin-hackers
> Subject: Re: [pgadmin-hackers] rule on view in pgschema
>
>
> In table class is present the remove routine. This routine
> have 2 parameter. The second parameter is 'RemoveSubItems As
> Boolean'.
> This parameter is from inserting also of the view?
>
> Public Sub Remove(ByVal Key As String, Optional
> RemoveSubItems As Boolean)
Not quite sure what you mean, but in 7.3 the dependency mechanism should
handle this anyway. You should probably add the same option to
Views.Remove though, if only for backwards comatibility.
Regards, Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2003-04-08 12:57:46 | pgadmin3 GTK |
| Previous Message | Dave Page | 2003-04-08 10:16:22 | Re: rule on view in pgschema |