Build 64 - 3.4 Final Beta
Build #64, 09/16/2008
NOTES
VistaDB.NET20.Web.dll (NEW)
The membership, and role providers have been rewritten. And we have a new profile provider as well. The new versions are able to be used within the ASP.NET Configuration Wizard for websites. You can edit roles and users using the configuration wizard. We will be adding documentation for process and some best practices for deploying the web.config very soon.
VistaDB Asp.Net Wizard (NEW)
This is a new tool to generate a VistaDB database that contains all of the correct schema for using the providers. It also supports updating an existing database from alternate schema to VistaDB 3.4 Providers without data removal. NOTE: Build 64 - This tool cannot currently update an existing database - we will have that ready for the final release.
SQL Server - If you have a sql server database that you migrated to VistaDB (Data Migration Wizard) this tool must be run to update the schema to the format we expect.
VistaDB 3.3 - If you have an existing VistaDB 3.3 membership database it must be updated to include the new schema for 3.4. This is an in place update without loss of current membership entries.
ISSUES AND FIXES
#924: Inserts from Stored Procedures are not applying column defaults - Problem was related to internal sorting of applied filters. Fixed
#925: TSQL Inserts do not apply specified Guid for PK Column, new id generated instead - Problem related to internal sorting of applied filters. Fixed
#679: Strange result from query - Fixed
#681: GetUTCDate() returns local time when used as column default - Fixed
#1051: Function - Error when base subquery returns no rows and column is set to a variable - The issue was actually a case statement issue where the underlying rows returned NULL (no records). The NULL would then attempt to be cast to a system bool (which has no concept of null). Corrected this behavior to return false when the underlying case would result in a null to bool conversion.
#1098: set default value to Stored Procedure parameter. You could not set a negative value on a bigint column as a default. Fixed
Comments
Jason Short on on 9.16.2008 at 3:17 PM
Just a quick note - the Serial Validator in this build is still just a simple string check. It is only looking for the length of your serial number. The final 3.4 release will require activation of the key.
Hans Nieuwenhuis on on 9.17.2008 at 10:53 AM
Good news! Are there also any improvements in performance?
Jamie Song on on 9.17.2008 at 11:41 AM
Looks like we had an install script error in Build 64. Under XP it was still checking for UAC. We updated the build to R2 (release 2).
From VistaDB 3.3 - 3.4 there are a lot of performance improvements. Our NUnit suite runs over twice the speed now.
Build 64 specifically has mostly rollups of bug fixes, and some internal changes for memory handling. There may be some others that I am not aware of though. There has been a lot of internal work on this release.