Re: NexusDb

On Thu, 28 Apr 2005 20:04:49 -0400, "Brian Moelk"
<bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>Then we will have to agree to disagree.

>> Part of the author's initial explanation of his review is :
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> DistcomSoft's databases contain more than 5 gigabytes of data and
>> because we mostly use SQL queries in our projects, SQL support is
>> crucial in any DBMS upgrade. Rather than rely on a system's
>> documentation, I decided to test each product with actual data and
>> queries to make certain it was compatible with our existing software
>> and to determine which supported the richest implementation of SQL for
>> future development. Hopefully, this data will be of some help to
>> others who need to replace their BDE software.
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

>The bottom line is that his statement about NexusDB V1 grossly
>mischaracterizes its transactional abilities. As evidence review your
>previous, incorrect assumption:

That may be and appears to be. Therefore, the correct position as I
see it is as follows :-

"Nexus Db1 SQL does not support Start Transaction, Commit, and
Rollback. However, this can be adequately catered for by simply
using the xyz component which does support this functionality. This
is a relatively small concession to make to achieve transactions."

Whether this means that the SQL transactions have to be
concatenated to achieve transactions, I still do not know.

I think that the "reviewer" can be justly criticized for not making
this clear. However by the same token, anyone that did a
review of Nexus Db1 and did not make this situation perfectly
clear, would not be doing the job correctly. IE. If they just
said "Nexus Db1 supports transactions in SQL".

I can accept my above quoted statement if it is true, and if
so it gives the complete and full picture. I think that is good
support for transactions. However, I think it is important to
state how this functionality is achieved.

By not stating this, I think that the author is not giving the full
picture. However, by the same token, I think that you were
avoiding stating this exact position.

If the above is all correct, I concede that Nexus Db1 supports
transactions, with the proviso that this is not completely
achieved by SQL statements.

I believe that Nexus Db2 does support these SQL statements.
If this is the case, I think that this is an improvement, and will
satisfy those people that require this in SQL rather than another
component.

I do not enjoy arguing with anyone, and I certainly do not
want the attention. I think if the position was more clearly
stated earlier on, it would have prevented many postings.

Brian
.

Relevant Pages

  • Re: NexusDb
    ... > At no time did I query your evaluation of the SQL statements. ... > That really only leaves the question of Transactions IMO. ... specific SQL commands that support starting, ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: NexusDb
    ... > The SQL standard is there partly to make application code portable ... if something is done outside of SQL ... having support for transactions outside of SQL does not ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: NexusDb
    ... >> That really only leaves the question of Transactions IMO. ... >> The only reason that I did not concede the point on transactions is ... >> buts, maybe's, no need to concatenate SQL statements. ... >transactional support using SQL or otherwise. ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: NexusDb
    ... << it does not support EXCEPT/INTERSECT, field auto conversion, IFNULL nor ... on other groups of queries NexusDB deservedly received a high score ... V2 SQL is highly compliant with the latest SQL standard - SQL:2003, ... a lot more features than exposed by the review you're referring to. ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Tiger Stock
    ... a lot of money selling applications based on their own platform. ... larger players support more interfaces, ... Coming back to a point in the last paragraph: Lack of support for SQL ... So if we take that off the table and compare companies, ...
    (comp.databases.pick)