Re: By The Dawn's Normal Light

From: Laconic2 <laconic2_at_comcast.net>
Date: Fri, 29 Oct 2004 17:09:37 -0400
Message-ID: <V-SdnWtyK9wGLB_cRVn-2g_at_comcast.com>


"Dawn M. Wolthuis" <dwolt_at_tincat-group.comREMOVE> wrote in message news:clu9qr$u8p$1_at_news.netins.net...
> "Laconic2" <laconic2_at_comcast.net> wrote in message
> news:zbqdna_fVJQZwx_cRVn-1A_at_comcast.com...
> >
> > "Dawn M. Wolthuis" <dwolt_at_tincat-group.comREMOVE> wrote in message
> > news:cltem0$alq$1_at_news.netins.net...
> >
> > > Where ordered lists are not implemented, users place ordering
attributes
> > > into the data. The predicates stay the same whether a user adds in an
> > > ordering attribute or the dbms software handles the ordering attribute
> > > (along with inserts & deletes to an ordered list). There is no change
> to
> > > predicates in this case. --dawn
> >
> > What's the difference between a list and an SQL cursor?

>

> A List is a logical type and not an implementation feature. I haven't
> worked enough with SQL cursors to know if they function the same as if
using
> an indexed list, but I suspect they do in some cases. However, if you
> decide you need an ordered list in SQL and you add an attribute to handle
> the ordering, then a SQL cursor will not help with renumbering your list
if
> you need to in order to accomodate an insertion, for example. Again, I
> haven't worked with SQL cursors enough to answer adequately, I
> uspect. --dawn
>
> Received on Fri Oct 29 2004 - 23:09:37 CEST

Original text of this message