Difference between revisions of "DataMaster 1.2.1"

From Protege Wiki
Jump to: navigation, search
m
Line 6: Line 6:
 
|CompatibleWith2=Protege-OWL_3.3.1
 
|CompatibleWith2=Protege-OWL_3.3.1
 
|CompatibleWith3=Protege-OWL_3.2.1
 
|CompatibleWith3=Protege-OWL_3.2.1
|CompatibleWith4=Protege-OWL_3.0
 
 
|CompatibleWith5=Protege-OWL_2.1.2
 
|CompatibleWith5=Protege-OWL_2.1.2
 
|CompatibleWith6=Protege-Frames_3.4
 
|CompatibleWith6=Protege-Frames_3.4
Line 16: Line 15:
 
<div style="float:left;">
 
<div style="float:left;">
 
== Detailed Changelog ==
 
== Detailed Changelog ==
* Bugfix caused by calling last() and other jumping calls on FORWARD_ONLY ResultSets returned by some databases (like Oracle), when querried for primary keys.
+
* Fixed bug caused by calling last() and other jumping calls on FORWARD_ONLY ResultSets returned by some databases (like Oracle), when querried for primary keys.
 
* Special (non-standard) sequence numbers for primary key columns are also treated.
 
* Special (non-standard) sequence numbers for primary key columns are also treated.
 
* More expressive warning messages when asking for Primary and Foreign Keys
 
* More expressive warning messages when asking for Primary and Foreign Keys
 
<br /><br />
 
<br /><br />
 
</div>
 
</div>

Revision as of 17:28, February 8, 2008

DataMaster 1.2.1

Dependency

The following dependencies exist for DataMaster 1.2.1:

not available

Changelog

see page for more details


Detailed Changelog

  • Fixed bug caused by calling last() and other jumping calls on FORWARD_ONLY ResultSets returned by some databases (like Oracle), when querried for primary keys.
  • Special (non-standard) sequence numbers for primary key columns are also treated.
  • More expressive warning messages when asking for Primary and Foreign Keys