This is an update to the VistaDB 3.6 preview builds as we continue to push forward towards release.
The Data Builder now has tabs support on the SQL input windows (yea!). And some minor display changes.
There are a lot of API changes in this build, but I think we are finished for changes to this version. The majority of the API changes were to complete the ripping out of the V-Index system that was non standard. It has been deprecated since VistaDB 3.2 or 3.3, and we are finally removing it.
We also changed the event handler and object class name for monitoring PRINT messages from your SQL Code. The help has a new topic on how to monitor SQL PRINT messages in your code. We changed the class to match the naming from SQL Server.
This installer will only be able to uninstall and upgrade 3.6 installs. If you are running any 3.6 prerelease you can just run this setup. If you are running any previous 3.x build you must uninstall it first before installing this build.
VistaDB 3.6 PREVIEW
Build #86, 07/01/2009
NOTES
The NUnit tests in this build have been updated. There are over 600 NUnit tests present in the current system.
IVistaDBCredential interface has been removed. This also removes it from any calls that may have had it implemented ( OpenDDA ).
DefineVIndex has been removed. It was only included for 2.x compatibility and deprecated since 3.3. VScripts are not supported in indexes at all - we have removed them from all index structures.
IVistaDBIndexInformation changed to remove the V-Index specific properties of the interface. They were not supported and flagged as deprecated. This also then chains down to all classes that implement this interface. DBStructure.IndexStructure is the most notable since it is returned by enumerating over indexes on a DDA Table.
Data Builder Changes
Data Builder has quite a few small changes and updates to dialogs. One of the most notable is that almost all of the forms that accept text input now support Tabs! You can Tab in your SQL query code and the tabs should be preserved now. The Line / Col display may not be quite correct in all situations since the engine does not know how to count the tab character. So error messages may be off by a few characters if you use tabs until we get all that working correctly.
Alter / Create table form Identity checkbox has been changed to render black when enabled and gray when not. This should make it easier to tell when you can check the box.
The Use Default Value in Update has been appended with (Not SQL Standard). This is one of the cases where we have a feature that SQL Server does not support. If you want to upsize to SQL Server at some point later the only way you can accomplish this feature is through triggers. We wanted to make sure it was labeled as non standard, and may eventually make a "strict" compliance mode that does not allow non standard features.
ISSUES AND FIXES
Changed the PRINT notification event and callbacks to match SQL Server naming conventions. The event is now called VistaDBInfoMessageEvent and VistaDBInfoMessageEventHandler.
TransactionMode=Ignore had a bug when a transaction was auto enlisted in a child execution. The rollback was reporting an error. There are no other known issues with TransactionMode Ignore at this time. We would appreciate any testing you may be able to provide on this feature.
OTHER NON TICKETED ITEMS
VistaDB.Diagnostic.Errors have had some changes to better english constants. The error numbers are all the same. Some of the error messages were also rewritten to not use ' at users requests for easier parsing from within CLR languages at runtime.
Documentation updates and changes.
VistaDBEngine classes will throw ReadOnlyExceptions upon user modification rather than NotImplementedExceptions (the engine class is readonly).
Subscribe