Release Notes for
           P4toDB, the Perforce Integration with SQL Databases

                        Version 2009.2
                          
Introduction

	This document lists all user-visible changes to P4toDB starting from
	the first release of 2009.2.

	P4toDB replicates Perforce metadata into an SQL database, enabling you
	to use your preferred relational database for reporting and analysis.
	This approach reduces the load on the Perforce server for these
	activities.

	Perforce numbers releases YYYY.R/CCCCC, for example, 2009.1/206108.
	YYYY is the year; R is the release of that year; CCCCC is the
	bug fix change level.  Each bug fix in these release notes is
	marked by its change number.  Any build includes (1) all bug fixes
	of all previous releases and (2) all bug fixes of the current
	release up to the bug fix change level.

	Please send all feedback to support@perforce.com

Requirements

	P4toDB requires a Perforce server at version 2009.2 or higher.

	Perforce server checkpoints and journals must be stored in uncompressed
	form.  They must have been created with the same version of the server
	that is being used for the replication.

	P4toDB is a Java program, and requires a full standard JRE 6 or later
	on the following platforms:

	  * Windows XP/2003/Vista/7
	  * Linux (x86)
	  * Mac OSX 10.5+ (Mac/Carbon)

	  The following are known to work by Perforce or Perforce customers 
          but are not tested or certified by Perforce or supported by Perforce 
          Technical Support (Certification Level 2):

	  * Solaris 8 (SPARC/Motif)
	  * Linux (x86/Motif)
	  * AIX (PPC/Motif)
	  * HP-UX (HP9000/Motif)
	  * Windows 98/ME/2000

	Supported target databases are:  Oracle 11, MySQL 5, SqlServer 2005,
	DB2 9 and Postgres 8.  The vendor's JDBC version 4 driver must be
	used.

Installation

	To install P4toDB, unzip the distribution archive into a location of
	your choosing.  You will need to put a JDBC 4 driver for any target
	databases you plan to use into P4toDB's "lib" directory.  

Configuration

	See the README.txt file for detailed documentation.

	To run it, start off by viewing the help output:

	   java -jar p4todb.jar --help

	The instructions there will tell you where to go next.  P4toDB requires
	a configuration file for its settings and sufficient SQL privileges to
	create tables.

--------------------------------------------------------------------------------
Major new functionality in 2009.2
	None

Minor new functionality in 2009.2

	None

Bugs fixed in 2009.2

	#249469 (Bug #39281)
	Date fields would be stored incorrectly when using MSSQL.  A checkpoint
	re-import is necessary to correct the data.

	#235979 (Bug #37884)
	Using a DB_PREFIX with upper-case letters and the DB_NO_REPL list could
	prevent replication from restarting.  Prefixes now must not differ only
	by case when using multiple replication.

	#233339 (Bug #37231)
	The PID_FILE is now treated as a semaphore to prevent concurrent running
	instances of P4toDB using the same configuration.

	#233164 (Bug #37641)
	The LOB datatypes for MS SQL Server have been changed from the
	deprecated IMAGE/(N)TEXT to VARBINARY(max)/(N)VARCHAR(max).

	#233150 (Bug #37640,#37606)
	Various documentation improvements such as moving the the JDBC driver
	connection examples out of the README and into the sample configuration.

	#233150 (Bug #37585)
	A non-default value for the PID_FILE variable is now treated as the
	explicit name for the PID file (no extra ".pid" appended.)

	#233150 (Bug #37463)
	The non-standard P4TICKETHASH variable has been removed.  Tickets are
	now handled in the standard manner.

	#232924 (Bug #37627)
	The FETCH_DELAY variable is now correctly acknowledged.

--------------------------------------------------------------------------------