Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

[PB9] performances

Status
Not open for further replies.

BBO007

Programmer
Jun 11, 2009
18
GB
Hi All,

Let say that I have an Oracle table of 10 fields with 3000 records in it.

I will read this table ans store its content in a datastore or in a structure.
I would like to know what is the more easy to manipulate and what is the more efficient : a datastore or a structure ?
I will need this object at anytime in the application, so there will be instance variables in an instancied non visual object, which will be instancied at the start of the application.

Can you give me your advice on this question ?
Thank you,
Thorben
 
Force of habit, but I'm going to say DataStore... It's what it's designed for.
 

yes Thorben is right:

quote:
I will need this object at anytime in the application, so there will be instance variables in an instancied non visual object, which will be instancied at the start of the application

I would define a global variable of type datastore:
they have all the advantages of being able to use functions as 'gds_my_datastore.Find( ".....", ..., ... )'

if your global variable is named: gds_messages (for example), then:

aplication object.open event:
----------------------------
gds_messages = create datastore
gds_messages.dataobject = 'dw_messages' // existing object
gds_messages.settransobject(sqlca)
gds_messages.retrieve()

application object.close() event:
--------------------------------
destroy gds_messages // as a good habbit

miguel l
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top