On Fri, Jul 12, 2002 at 10:45:06AM -0400, Jim Parker wrote:
> I'll try to be a little more specific.
> ...
BTW which datatypes are you using in PGSQL?
> The second way I have thought to do it is to include the vertex table in
> the first query. This would give all the information I need, but would
> require addition processing to distill the x, y, z information from the
> color, size, etc. information I get form the first truple.
Sorry, I still do not really understand that. Well maybe that's due to
me answering mails while doing something else, but anyway, it would be a
wise idea to let SQL handle as much of the work as possible.
> The first method requires ( I believe ) me to open a cursor. Retrieve the
> truples, allocate memory for a vertex array, Open a cursor to get the
> vertex info put into array, add data to linked list, close second cursor,
> look at next tuple in first cursor.
Which certainly doesn't pose a problem.
> the second method is to open the cursor retrieve data from first tuple, get
> next tuple, check polyine id, if same as current get x, y, z info.
>
> It seems to me the first method is pefered way of doing things. Is there
> an easy way to do it ?
I'm really at a loss guessing what you mean here. Where's the problem?
You did describe your solution in a way that implementing should be
straightforward.
Michael
--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
