Complex Folders Vs Database Views - Discoverer 10g

Question

Hello All,
The way complex folders works is almost similar to creating a database view and using that to create a custom folder.
So could someone advise wrt peformance etc which is a better option ?
Creating complex folders gives the flexibility to change whatever changes are rqd using disco admin and does not reqd even logging to which incase of DB views would need to be done to recreate a view incase of any changes. But would like to weigh down both the options on other parameters.
One thing i see is implementing oracle apps security is easier using DB views...but again..i could create custom folders using select * from table where gl_security_pkg concept and then create complex folders using these folders ?
Any thoughts would be helpful
Thanks.
Message was edited by:
vishalg

Answer 1

Vishalg.
The way I've always considered it is as follows:
1. I prefer not to be 'married' to one tool (ie: Disco) and therefore always recommend writing database views over custom / complex folders if possible. That way, database tools such as TOAD, SQL Nav, SQL Dev, etc. can also use the view (not to mention Oracle Reports, etc. as well).
With that in mind, I try to have most folders just pointing to a database view and all the 'fine tuning' done in the folder (ie: column order, hierarchies, security, etc.).
2. I do use custom folders when it's a LOV that's used in an item class. For example, you could create a simple LOV in a folder on an item, by just using that item for the source and the output. However, if it's a big dataset or you want to go to another table that's small and just has the distinct values for example, a custom folder is perfect for creating (I always put a _LOV extension on the folder name so I know) and setting an item class against.
Sometimes though, I've created a LOV for the list and then have just brought it in to a folder by simply pointing to it. It's the same kind of consideration in 1. above - if I'm creating a system that may be used by other tools - or God forbid - a client wants to move to another query tool like Cognos, BO, etc. then all the views are already there in the database and you just have to build their version of the middle layer (ie: catalog, universe, etc.).
3. I don't think I've ever had to use a complex folder. The concept is good though as in you can have 2 folders that are joined, but you want to create another folder that only has certain fields from each of the original 2 folders and that's the one a user uses.
But same consideration as above. Do I want to completely customize the Disco EUL, or use it more as a 'delivery device' (hey ... good term!).
One other big consideration for all this is that if you work in a shop where they have a big (read obnoxious) DBA who doesn't "allow views in his database" (been there), then you can always do the custom / complex folder thing from within Disco Admin and keep the DBA happy. However, once he's fired for being obnoxious and then new "touchie-feely" DBA comes on board, you may curse why you had to create a custom EUL in the first place.
All just your point of view, but I'm a view guy all the way.
Russ