Re: Developer 2000: Why use Object ID instead of Object Name?

An object id is an internal pointer to your object. If you use a name instead of the object id, forms needs to convert the name to an adress(same as the find_object does) of course this takes time.

A good reason to use object id's is performance, for instance if you want to refer to the same object twice in the same procedure, you better get the id first and then refer to the object via the id.

If you only refer 1 time in your procedure to the object performance will be the same.

Another reason is that with the is_null built-in you can check wheter or not your object exists.

If you only
John Haskins <76054.334_at_compuserve.com> heeft geschreven in bericht <75a9e9$r2v$1_at_news-2.news.gte.net>...
>I'm working with Developer's built-ins and noticing that many of them
accept
>either an object name or an object ID as input. Why go to the extra
trouble
>to create a variable to store the object ID, extract the object's ID with
>FIND_objectname, and then use it? Since you have to know the object's name
>to get the ID anyway, it seems it's easier to just use the name and be done
>with it.
>
>Opinions on this are welcome...I'm sure there's some reason Oracle went to
>the trouble to make this feature available.
>
>
Received on Fri Dec 18 1998 - 23:34:12 CET