>>Mark, interesting that Informix is using a non-standard version of
>>SQL as a selling point. Granted, if it is adopted in the next 2
>>years, Informix may have an edge. But if its not then they are
>>proprietary at the SQL level.
Dave, I am surprised that you even bother with using this argument, because all vendors have non-standard extensions to ANSI standards, especially in the emerging areas. IFMX is trying to stay as close to the draft standard as possible, and used the integration of Illustra into IFMX as an opportunity to clean inconsistencies created as the SQL3 standard was moving through different drafts. On the other hand, can you remember the difficulties that Sybase's implementation of triggers caused people because it was non-standard; I know Sybase was proud of it because they claimed to have been the first to implement triggers, long after everyone else had them.
As for your other questions.
1. Informix has announced (and released?) capability of supporting Datablades written in or using Java. I do not know the details.
2. SQL3 and Java are not mutually exclusive. Java, C, C++, ... are used to write what are known as DataBlades, Cartridges, Java Beans, or whatever other specialty extension that the engine may support. SQL3 is the query language and may also be used to create additional data types, including such things as collections of data (including the extensible data types, like those created in Datablades, ...).
3. It appears that you are saying that you will only be able to support rowtypes, sets, and arrays only in the special extensions created using Java, and not also in SQL3. Is this what you meant in response 9?
Mark |
