# [EMAIL PROTECTED] / 2005-07-22 13:04:27 +0200:
>
>
> > # [EMAIL PROTECTED] / 2005-07-22 09:10:01 +0200:
> > > > # [EMAIL PROTECTED] / 2005-07-21 19:11:04 +0200:
> > > > > I use some updateable views to handle my data (which are
> > > > > amazingly slow), which gives me ultimate flexibility to
> # [EMAIL PROTECTED] / 2005-07-22 09:10:01 +0200:
> > > # [EMAIL PROTECTED] / 2005-07-21 19:11:04 +0200:
> > > > I use some updateable views to handle my data (which
> are amazingly
> > > > slow), which gives me ultimate flexibility to handle my data.
> > > >
> > > > there are some insert ru
# [EMAIL PROTECTED] / 2005-07-22 09:10:01 +0200:
> > # [EMAIL PROTECTED] / 2005-07-21 19:11:04 +0200:
> > > I use some updateable views to handle my data (which are amazingly
> > > slow), which gives me ultimate flexibility to handle my data.
> > >
> > > there are some insert rules which use curr
> # [EMAIL PROTECTED] / 2005-07-21 19:11:04 +0200:
> > I use some updateable views to handle my data (which are amazingly
> > slow), which gives me ultimate flexibility to handle my data.
> >
> > there are some insert rules which use currval() to get the last
> > sequence id for my data which I h
# [EMAIL PROTECTED] / 2005-07-21 19:11:04 +0200:
> I use some updateable views to handle my data (which are amazingly
> slow), which gives me ultimate flexibility to handle my data.
>
> there are some insert rules which use currval() to get the last
> sequence id for my data which I have to inser
Hi all,
I'm still working on my updateable views, which work fine now even I have a
trigger to use because my delete rules wont work, but thats not my current,
more important problem.
I use some updateable views to handle my data (which are amazingly slow), which
gives me ultimate flexibility
