| >> When using Dynamic SQL, Rdb/VMS allows prepared statements to be reused
>> across transaction boundaries. With INGRES, you must re-PREPARE the
>> statement for each transaction. This is a dramatic performance hit.
>>
>> Since most interactive tools work with a database system through the
>> Dynamic SQL interface, this gives Rdb/VMS a big advantage. It also explains
>> why INGRES' tools generate 3GL code which is then compiled, rather than
>> using Dynamic SQL.
What are the implications of this for customers using Ingres Tools for Rdb?
Rick C
|
| Ask in the INGRES TOOLS conference, but I will bet that (at least
currently) it means that applications developed with the INGRES TOOLS do
not take advantage of this Rdb/VMS capability.
Since we are involved in both cooperation (INGRES TOOLS, ULTRIX/SQL) and
competition (VMS Databases) with RTI, we are always in a funny
situation. For example, RTI has been made aware of the impact this
particular behavior of theirs has on some software we want to port from
VMS to Ultrix. So, we hope they will fix it sometime soon. Of course,
once they fix it for ULTRIX/SQL, the fix will also become available for
INGRES on VMS, negating this competitive advantage. Sigh.
|