|
|
Posted by Jerry Stuckle on 04/03/07 03:51
Simon Stienen wrote:
> On 2007-04-03 04-52-47, Jerry Stuckle wrote:
>> Not at all a bad design. Any class will do the same thing. It handles
>> a single query. If you make another query, that will overwrite the
>> original query. If you want two concurrent queries, you use two db objects.
>
> One query per _DATABASE_? Sorry, but I think this is a somewhat limited
> approach.
No, the DB object represents a QUERY. You can have one QUERY open at a
time. This is pretty standard for objects - each instantiation handles
a specific object.
In this case the DB object represents a query (and its results), so you
can have one query open at a time per DB object. The same is pretty
true in all OO languages. I've used similar in C++, Java and even VBScript.
It's all in understanding the purpose of the object.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|