Performance Question

[caseye]

This is a novice question.

We are developing a piece of software for database access and we are creating Custom Data Objects that interface with the Database. The Idea behind these objects is to make them univeral so they may function in stateless or stateful environment. This will allows to easily update our ASP Servers and all our desktop clients with the same files.
Once the objects have pulled the data they close the recordset and store the data in local variables and if there are changes made then the data it is updated back to the server.

Here is my question:

We have a WorkOrder_Main Table which holds the main WorkOrder Info, then there other work Order Tables such as parts

the system keeps track of all inventory and in the workOrder parts Table there is the WorkOrderID and PartID and the quantity used the workOrder object will query the parts table and get the partIDs then looping throught those part ID it will Create a collection of part objects. At each creation of these objects the objects will run a query using these IDS and populate the properties of these objects with data from the Parts Main Table. This would mean 15 to 20 connections for just parts which would mean that an entire work order could consist of many connections. Is there any performance or connection issues that I could expect to face, or does someone have a better Idea that I could maybe use.

Thanx in advanced.

 

[crystalized]

We have a similiar although slightly different system. Within each of our data objects we have a selection of different ways to retrieve the data. For example we have Select which retrieves a single record then instantiates the object which is returned by the function (our functions are static so they are callable directly without need for an instance). But we also often have SelectBySomething function that selects a group of records based on some criteria, then instantiates all the objects and puts them in an Array which is returned from the function.

Additionally we have a business layer. In the business layer I have one class that is essentially a Weak Entity table and within it I have a project and user object as parts of it's members. The project and user objects are instantiated only when they are needed (so when someone "gets" them they instantiate so the user can refer to properties of that object - which of course is what you often want when working with a weak entity table)

So in the end I guess what I am saying is that you may want to consider adding additional ways of selecting your data within your data objects.

I hope this helps Crystal
crystalized_s@yahoo.com

--------------------------------------------------

Experience is one thing you can't get for nothing.

-Oscar Wilde

 

[caseye]

Well the intention is to also hava a function that works similar to they way you specify a conection string
I want to use a delimeted string that has Field aliases and values for those fields the interfacce will the parse the string and lookup the field aliases and retrieve thier information such as table, fieldname, data type, and length then with that information the object will build a query an in the case I am searching for parts or a sub-object the query will start at that point, pull and group the records according to the condition then lookpup the work orders or Parent object. Then Create a hierarchy of objects that allow full manipulation of the data. The objects will also allow the return of XML data for the ability to integrate with other systems or use the HTTP.request to remotley retrive data without having to worry about fire walls.