Quote from cwb1014:
Hey, srv, if you get a chance to address the issue above, that would be great! Sure would like to have your insights in view of your familiarity with the database! Thanks in advance.
cwb1014
I really couldn't offer anything to try that would be accessible to the end user.
It would be presumptuous to make suggestions in this area to the developers; I'm unfamiliar with the internals of i/rt.
I meant to say that the problem is NOT that they are using the wrong tool or an inefficient tool. A database can be implemented using a database ENGINE, such as dbVista efficiently or otherwise depending on the knowledge, skill, and experience of the programmer.
I have been out of the game for over 18 years. At that time at least, the thinking was design issues were most often the cause of software failure (problems in the general sense) - and implementation issues more often than not followed from poor design decisions.
(Continuing to the absurd: poor or incomplete specifications invariably result in poor design; inadequate or incomplete domain expertise/knowledge makes good specifications impossible, at best a matter of luck.)
By analogy: I doubt choosing the C programming language, (because it is "so old") might have something to do with a performance problem.
On the other hand, lack of expertise in the C programming language could result in serious performance problems.
An application developed in Java (or C++/Fortran/Basic) might be superior to that application implemented using C; if the Java programmer is expert using Java and the C programmer has little skill with C.
IOW, don't blame the tools.
dbVista supports the "network" model, as opposed to a "hierarchical" or "relational" model. In a sense it is a lower level tool than a relational database engine; just as C is lower level than C++ or Java. My recollection is that Raima was working on an SQL front end as that's what programmers were being taught and were familiar with; the relational model was achieving dominance, making everything else a speciality or niche product/expertise. If i/rt is using an SQL wrapper around the underlying engine, then all bets are off as it seems unlikely a 'network model' database engine made to look 'relational' is as efficient as an engine designed to be relational to begin with.
AND - its been 18+ freeking years since I've had my head in this stuff... I don't know what i've forgotten - let alone what progress has been made in the last two DECADES...
That's all I got!
Ready for flames and charges of irrelevance...
