Invisible wrote:
> Given time, you could probably integrate the entire thing into one giant 
> SQL statement. You'd probably find that you can actually simplify it 
> down to something rather smaller once it stated all in one operation. 
> And that the DB engine can do some pretty impressive optimisations after 
> that too.

Yeah, that's why I'm after it.

On the other hand, I've done SQL statements that I gave up on after 
they'd run for a couple of days, recoded it as a "SELECT *" without a 
where clause, calculated the new column, and wrote it back, and *that* 
ran in about 90 seconds.

(Basically, a bunch of streams, each with an event having a start time 
but no end time. Each event ends when the next event starts on the same 
stream. Assign the "duration" column to any row that doesn't have a 
duration and isn't the most recent record for that stream.)

> OTOH, if you haven't got enough time to do it... what can you do?

Post to p.o-t too much?

-- 
   Darren New / San Diego, CA, USA (PST)
     On what day did God create the body thetans?

Post a reply to this message