VistaDB 3.4 Build 63 Development

written by Jason Short on Friday, July 18 2008

Build #63, 7/18/2008

NOTES

We now have over 600 NUnit tests!  New tests are being added for SQL code syntax comparing to SQL CE and SQL Server.  Not all syntax will be added, but there are some changes on the way for sure.

The Data Migration Wizard has been changed to allow it to run on 64 bit Vista.  Simple fix.  The app was set to CPU Any - that meant it would JIT to 64 bit.  The problem is that the old VistaDB 2 runtime was only 32 bit.  Trying to load it meant you blew up pretty quickly.  Also updated DMW to state version 3.4.  Tested for SQL CE 3.1 only (built in VS 2005).  A SQL CE 3.5 version will come later after the 3.4 release. 

ISSUES AND FIXES


 #40: Opening a table with 1024 columns in DataGridView - Issue is with an internal limit to the FillWeight in the DataGrid control. Added work around to force the fill weight to be 1 on column creation. This allows the code to run without issue.

#151: DataBuilder > XML Export - Root Element Naming - Change was to the engine, not the databuilder. Altered the export code to make sure the name used is only the filename portion and not the full name of the file.

#223: While viewing Data folder in Data Builder tree view there is no refresh button and F5 does not reload the grid - Added refresh button with icon and F5 hotkey to data viewer.

#755: Identity Column Type bigint and @@identity - IntColumn now correctly looks at the inbound object type prior to attempting conversion.

#709: CLR Proc which return a Table - Fixed sample for CLR Procs.

OTHER NON TICKETED ITEMS

CF framework strikes again - several of our fixes didn't work on the CF and we had to dumb them down.  The CF compiler apparently doesn't know how to support function prototypes that use a default param on a function type.  Wierd, they make you explicitly set it anyway.  And they decided to hide the Dispose method on the Filestream (private).  WHY?  Using() still works, but any other use and you can't dispose of it.  Just Close() it and hope for the best.

INTERFACE CHANGE

New public Interface IVistaDBTableList - this is used as an experiment to extending the DDA interface to include strongly typed members.  This interface gives you the ability to get back a strongly typed version of the EnumTables through a function called EnumTablesTyped().  This will return an IVistaDBTableList that may be used in a foreach loop for faster handling without casting, and contains optimized lookups for contains, etc.

IVistaDBDatabase db = DDAUtils.BuildTestDatabase(ref DDAObj, dbname, false, null, false);
IVistaDBTableList tableList = db.EnumTablesTyped();
foreach (string table in tableList)
{
    Console.WriteLine("Table is named: " + table);
}

Similar Posts

  1. Exposing strongly typed interfaces that are not CLS Compliant
  2. VistaDB 3.3 Build 56
  3. The GC does not solve all memory leaks

Comments are closed

Options:

Size

Colors