Pervasive PSQL v11 SP3 ADO.NET Data Provider Release Notes
Update Release – May 2013

Contents

This file contains the following topics:

About Pervasive PSQL ADO.NET Data Provider

Pervasive PSQL v11 SP3 provides three versions of the ADO.NET Data Provider, versions 3.2, 3.5, and 4.0. All versions are installed by default with the database engine.

The Pervasive PSQL ADO.NET Data Provider runs as 100% managed code and can run and connect to the database entirely within the common language runtime (CLR).

System Requirements

Installation of the correct .Net Framework version
Repair of the Pervasive PSQL installation

Note  See About Pervasive PSQL ADO.NET Data Provider for information about which version of .Net Framework is required for each version of the ADO.NET Provider.

Features In The Current Release

See the section “What’s New in this Release?” in Pervasive PSQL Data Provider for .NET Guide for the new features.

Getting Started

The files required for the Pervasive PSQL Data Provider for ADO.NET are provided through two different installations. The Provider assemblies are included by default when the Pervasive PSQL database engine (all editions) is installed. The design-time files, sample source code, templates, and libraries, are included in the software development kit (SDK) installation for the ADO.NET access method.

Provider Assemblies

The installation of the database engine copies the Provider assemblies to version-specific directories under the PSQL\bin directory in the 32-bit PSQL installation location. Separate directories are used for 3.2, 3.5, and 4.0.

If the installation detects a supported version of the .NET Framework, the following also occurs:

The generic Provider instance (Pervasive.Data.SqlClient) always points to the latest Provider assembly.

The Provider assemblies copied to the PSQL\bin directory are not pre-compiled at install time. That is, they are not added to the Windows native image service on the local computer. If you include the Provider assemblies as private side-by-side assemblies installed with your application and want them added to the Windows native image service on the target system, your installation must add them. Refer to the topic “Native Image Service” in the Microsoft MSDN Library.

Note  If the installation of the database engine detects any Pervasive PSQL ADO.NET Data Provider prior to version 3.2, the older Provider is uninstalled.

Design-time Files

The design-time files needed for the different Pervasive Membership Providers for ASP.NET and Visual Studio integration are available via Web downloads from the Pervasive Software web site. Each assembly version has its own SDK installation executable. See http://www.pervasivedb.com.

The Membership Providers should be installed on the computer where .NET application development will be performed, and also on the client computer(s) that will execute the application.

Each Membership Provider is installed to the GAC during the installation process.

Referencing the Different Providers

In addition to installing the sample source code files, templates, and libraries, the SDK installation executable also performs the following integration for the Pervasive PSQL ADO.NET Data Provider:

Installing Visual Studio After Installing the Pervasive PSQL ADO.NET Data Provider

If you install Visual Studio after installing the Pervasive PSQL ADO.NET SDK, re-run the SDK installation executable. The SDK installation integrates the Pervasive PSQL Membership Provider with Visual Studio.

Logging Application Block Configuration

For the Logging Application Block to function correctly, you must include the following line in your application:

ConfigurationManager.GetSection("Pervasive.Data.SqlClient.Entity");

Design Considerations

The following information can help you decide how you want to design your application to function with the Pervasive PSQL ADO.NET Data Provider.

Design Method
Comments
Application references the generic Provider instance Pervasive PSQL Provider
  • Application can use updates to the Provider released by Pervasive without being recompiled.
  • Application does not need to distribute the Provider files.
  • Application always uses the latest assembly version installed in the GAC by the Pervasive PSQL installation and updated by Pervasive PSQL patches.
Application references a version-specific Provider instance such as Pervasive PSQL Provider v3.2, Pervasive PSQL Provider v3.5, or Pervasive PSQL Provider v4.0
  • Application always uses the latest patches for a particular version of the Provider installed in the GAC.
  • Application will not use new releases of the Provider installed by Pervasive PSQL.
Application references the Provider’s strong name (a name that consists of an assembly's text name, version number, and culture information (if provided), with a public key and a digital signature generated over the assembly).
  • Application distributes that specific version of the Provider.
  • Application installs the specific Provider as a private side-by-side assembly in the application installation folder.

Membership Provider for ASP.NET 2.0

The ASP.NET Login controls use the custom Pervasive Membership Provider to specify a separate database for storing user information.

Additional information about writing a custom membership provider is available at http://msdn2.microsoft.com/en-us/library/f1kyba5e.aspx.

See Libraries for the location of the Membership Provider.

The sample ASP.NET application included with the libraries and samples shows how to create users, change passwords, recover passwords, and validate users.

Libraries

The SDK installation executable copies the following libraries to version-specific directories under the PSQL\bin directory. (See also “Where are the Pervasive PSQL files installed?” in Getting Started with Pervasive PSQL.)

Library
Description
PSQL.Membership.Provider.dll
Allows the ASP.NET Login controls to use a PSQL database.
PSQL.VisualStudio.DataTools.dll
Used by the VS.NET development environment for Server Explorer integration.

Samples

The following table summarizes the samples provided with the Membership Provider. By default, the SDK installation executable copies the sample files to version-specific directories under the All Users\Application Data\Pervasive Software\PSQL directory. Note that the “application data” location varies depending on the bit-architecture of the operating system. See “Where are the Pervasive PSQL files installed?” in Getting Started with Pervasive PSQL.

Folder
Sample
Purpose of Sample
C#
CommandBuilder
Creating a command from an SQL statement
CreateDatabaseObjects
Creating database objects such as a table or stored procedure
DataAdapter
Using the data adapter to read or modify data
DataGridUpdate
Updating data in a grid control
DataReader
Using the data reader to get data
Escapes
Processing escape functions in statements
LimitingRows
Limiting the number of rows returned in a result set
LocalTransactions
Processing a transaction
LongDataTypes
Using long data types such as LONGVARCHAR
ScalarValue
Executing scalar functions to return a value
StoredProcedures
Using stored procedures
MembershipProvider
ASPX files for using the membership provider with the ASP.NET Login controls
Various login activities, changing password, and so forth
VisualBasic.NET
Same type of examples as listed for C#
Same as for C#

Membership Provider Requirements

Steps to use the Membership Provider

Login Controls within ASP.NET will now use the Pervasive Membership Provider.

Users Table Script
CREATE TABLE Users 
( 
  PKID UniqueIdentifier NOT NULL PRIMARY KEY, 
  Username Char (255) NOT NULL, 
  ApplicationName char (255) NOT NULL, 
  Email Char (128) NOT NULL, 
  Comment Char (255), 
  "Password" Char (128) NOT NULL, 
  PasswordQuestion Char (255), 
  PasswordAnswer Char (255), 
  IsApproved SmallInt, 
  LastActivityDate DateTime, 
  LastLoginDate DateTime, 
  LastPasswordChangedDate DateTime, 
  CreationDate DateTime, 
  IsOnLine SmallInt, 
  IsLockedOut SmallInt, 
  LastLockedOutDate DateTime, 
  FailedPasswordAttemptCount Integer, 
  FailedPasswordAttemptWindowStart DateTime, 
  FailedPasswordAnswerAttemptCount Integer, 
  FailedPasswordAnswerAttemptWindowStart DateTime 
) 
Example Modified WEB.CONFIG
<connectionStrings> 
<add name="PsqlServices" 
connectionString="ServerDSN=ASPNETPSQL;" /> </
connectionStrings> <system.web> 
<membership defaultProvider="PsqlMembershipProvider" 
userIsOnlineTimeWindow="120"> 
<providers> 
<clear /> 
<add  
name="PsqlMembershipProvider"  
type="PSQL.Membership.PsqlMembershipProvider"  
connectionStringName="PsqlServices" 
enablePasswordRetrieval="true" 
enablePasswordReset="true" 
requiresQuestionAndAnswer="true"  
writeExceptionsToEventLog="true"  
debug="false" 
passwordFormat="Clear"/> 
</providers> 
</membership> </system.web>

IPv6 Environment

The Pervasive PSQL ADO.NET Data Provider 3.5 and Data Provider 4.0 support IPv6 environments (IPv4/IPv6 mixed or IPv6-only). Unpredictable results can occur if you use previous versions of the Data Provider in an IPv6-only environment.

Documentation

To help with the development of your .NET applications, see Pervasive PSQL Data Provider for .NET Guide and Pervasive.SQL Programmer’s Guide in the Pervasive PSQL SDK documentation.

Known Issues

All known issues for Pervasive PSQL v11 SP3 are published on the Pervasive web site. See http://www.pervasive.com for the latest Known Issues.

Technical Support

You may obtain technical support from the following Web-based support options:

Disclaimer

PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN "AS IS" BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT.

Copyright ©2013 Pervasive Software Inc. All Rights Reserved.


Pervasive Software Inc.
http://www.pervasive.com
12365 Riata Trace Pkwy, Bldg B
Austin, TX 78727 USA
Voice: (512) 231-6000
Fax: (512) 231-6010

*** End of Release Notes ***