Re: best way to fetch next/prev record based on index
От | Greg Stark |
---|---|
Тема | Re: best way to fetch next/prev record based on index |
Дата | |
Msg-id | 87y8l4rujq.fsf@stark.xeocode.com обсуждение исходный текст |
Ответ на | Re: best way to fetch next/prev record based on index (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: best way to fetch next/prev record based on index
|
Список | pgsql-performance |
Tom Lane <tgl@sss.pgh.pa.us> writes: > The only reason the code in parse_expr.c appears new is that the > functionality used to be in gram.y. Ah, that was what I was missing. Though it's odd since it seems there was code in parse_expr.c to handle the "=" case specially. > I'd like to see this fixed to comply with the spec, but given the lack > of complaints about the existing behavior over so many years, ripping > it out meanwhile doesn't seem appropriate. I tried my hand at this last night and think I did an ok first pass. But I'm missing one piece of the puzzle to get it to compile. What do I need to know to be able to construct a List* suitable for passing as the second arg to make_op() knowing only that I want to create a List* to represent "=" or "<" or so on? I also had another question I didn't ask in the other email. In the midst of a forboth() loop, how would I tell if I'm at the last element of the lists? Would lnext(l)==NULL do it? -- greg
В списке pgsql-performance по дате отправления: