Re: Power Objects V2.0

Tomas Gardson wrote:

> If you are using a repeater control and a sqllookup for a field, be aware
> to that OPO have to make a sqllookup for every row in the repeater control.
> If you for exampel use 3 sqllookups to get values in a repeater control
> with 100 rows, OPO needs to make 100 x 3 = 300 sqllookups on every refresh
> of the repeater control. This is slooooow.

I agree with you that a repeater issues SQL statements for each row for each SqlLookup(), but depending on your RowFetchMode, the repeater doesn't have to retrieve all the rows when it gets refreshed.

[Quoted] > I use ECEX SQL to do fast database maipulations and to write PL/SQL blocks.

I use EXEC SQL too, but when you use it, you also lose the connection with the OPO session, so things like IsWorkPending() will not pick up any changes. I think its fine for discrete database manipulations, but I caution against using it too much.

In version 2, you can use PL/SQL with a standard recordset.

> > Hi Tomas-
> > So your the guy with the other copy OPO! :))
> >

[Quoted] Oh man, don't say that! I am the author of a new, advanced book on OPO called Mastering Oracle Power Objects, available from O'Reilly and Associates at http://www.ora.com. I think it's a good book, and I hope it sells more than 2 copies!

My last book, the Oracle Power Objects' Developers Guide, sold about 10,000 copies, so there are either 9,998 people out there absolutely desparate for something to read or more than 2 OPO developers.

• Rick Greenwald greenie_at_interaccess.com