This table lists the most recent releases of Texpress 8.2 for each platform.
Select the Number in the Version column for Release Notes.

Top

Release Notes

8.2.008 - 30 June 2010

• Note Texpress 8.2.008 or later must NOT be used with any EMu version pre EMu 4.0.02.
• The XML auditing facility no longer audits display only fields linked in from remote tables.
• The TexAPI file transfer calls (TexFileGet() and TexFilePut()) do not support files larger than 2 Gb. The API has been altered to allow files greater than 2 GB to be transferred. The change requires TexAPI 6.0.001 or greater and Texpress 8.2.008 or greater, otherwise the API defaults back to supporting files up to 2 Gb.
• A new Texpress option authadmin indicates whether the admin password (as supplied by the texserver -a option) should be checked if the user entered password fails. The default setting of yes provides backwards compatibility with older versions of texserver. If the option is set to no the user's password must be supplied correctly to authenticate.
• Major improvements to form expression evaluation. In particular the evaluation of dependent assignment expressions (where the value of one field depends on the value of another) has been improved.
• A new Texpress option refkeyeval indicates whether reference fields (copy links) should be cleared when the reference key (link key) is empty. A value of full forces all reference fields to be cleared before the key lookup. If the key lookup fails or the reference key is empty the reference fields remain empty. A setting of historic will leave existing data in reference fields if the key lookup fails or the reference key is empty. The default value is full.
• A new command is available in texdesign when the Texpress option guru=yes is enabled. The Define->Reference key evaluation command is used to set the new refkeyeval value on a table wide basis. A value of historic forces data to be left in reference fields when the key look fails or the reference key is empty regardless of any attempt to override the setting.

8.2.007 - 12 March 2010

• Users may be able to see records that should be restricted by Record Level Security (RLS) where multiple fields are defined for the security profile. The correct records are now displayed.

8.2.006 - 24 February 2010

• The texadmin configuration page may appear to hang (infinite loop)  when generating a configuration for a table with a very large standard deviation between the number of atoms per record. A suitable configuration is now generated.
• An empty initialised table may cause texadmin to fall over when calculating an optimal configuration. A suitable configuration is now generated.
• The Texpress option guru=yes must now be set for texdesign to prompt to reassign internal numeric ids. The change will avoid inadvertent reassigning and its severe consequences.
• The TexFSRemove() API call has been extended to allow symbolic links to be removed.

8.2.005 - 30 December 2009

• Added new server function to retrieve a Texpress option value. The function signature is TexOptionGet(char *dbname, char *opt, char **value), where dbname is the table name, opt is the name of the option to be retrieved and value is a string pointer into which the return value is placed. 

8.2.004 - 22 October 2009

• Fixed issue in texql.pm where reading boolean data may lead to incorrect values being returned for any column after the boolean column.
• The error message Column "xxx" not a base KE Texpress table may be returned when end-of-file is reached on a cursor where the resulting query table is a synthesized table (e.g. distinct, times, union, etc).
• A less than optimal table configuration may be generated after running texcompact and before the table is rebuilt. An optimal configuration is now generated.

8.2.003 - 29 September 2009

• For tables with data file > 2Gb in size a potential multi-user file write error was corrected.

• The index diagnostic program texrddump was extended to provide more readable output as well as information on the oflow file.

8.2.002 - 08 September 2009

• The upgrade program (texupgrade) did not reindex empty tables when upgrading from Texpress 8.1 to Texpress 8.2. The tables required a reindex due to changes to the record descriptors. Empty tables are now reindexed.
• Fixed issue where changing the table configuration by hand (in particular the number of records per segment) may result in a less than optimal configuration being generated next time automatic configuration is run.
• A large number of defunct processes may be produced if a file tries to grow beyond the maximum number of partitions. The defunct processes are now cleaned up correctly.
• Changed texlock to display the name of the program that cannot be run when an error occurs.
• Changed texload to work around an optimiser issue in gcc 4.1 and 4.2. The issue caused a spurious character to be  added to the data read from the input file.
• Adjusted XML audit information to not dump columns that do not contain data and have not been modified.
• Fixed problem with bad code being generated by gcc3 and gcc4 for texload. The bad code resulted in a spurious character appearing as the first character read after a new tinto file is opened.

8.2.001 - 13 July 2009

• Improved self-configuration of table indexes. Indexing information is now maintained on a per record basis allowing the generation of more efficient configurations. The indexing utilities texconf, texanalyse and texdensity have been updated to use the new information.
• Index parameters may be set in the params file in the database directory. The parameters allow the indexes to be tuned, although in most cases tuning is not required.
• Fixed issue where duplicate key values may occur if a user cancels a record insertion and then edits an existing record.
• Fixed regular expression code ([\200-\377]) so that top bit characters can now be part of character ranges.
• Added support for $user as part of the tag in Record Level Security profiles. The variable is replaced with the user name of the person logged into the server.
• Added -d command line option to texchdba to specify the old DBA user account is to be deleted.
• Replaced index hashing engine to reduce the number of "false" matches generated due to hashing clashes.
• Increased the level of precision maintained when converting latitude and longitude values between degrees/minutes/second and decimal degrees representations.
• Improved auditing performance by changing xml output to be unbuffered.
• Changed default output formats for latitude and longitude types to allow a variable number of digits after the seconds decimal point.
• Fixed up issue where setting readonly=yes in a table opts file or via dbnameopts would not mark records as readonly via Record Level Security.
• Improved file transfer speed when sending/receiving files via TexAPI.
• Changed the default setting for autokeyreuse to Unallocated. Keys are now reused by default.
• Added database option saveinvalid to allow TexAPI based programs to update and save records that would otherwise fail validation.
• Updated fifo() interpreter call to have better error handling if the fifo or lock files do not exist.
• Changed texload to wait indefinitely when trying to update a record that is being modified by another user. A new option, loadtimeout, may be used to modify this behaviour. A value of zero (0) forces texload to wait until the record being changed is either saved or released. A value greater than zero is the number of seconds to wait before reporting an error and moving to the next record.
• Extended phrase based searching supported by texformsand useable with Record Level Security. Support added for:
  • NOT (!) phrases (e.g. !"Blue Windows")
  • STEM (~) phrases (e.g. ~"walking slowly")
  • PHONETIC (@) phrases (e.g. @"George Brown")
  • EXACT (=) phrases (e.g. ="Bill smith")
  • NOT within phrases (e.g. "!Blue Window")
  The allowable syntax for searches is:
          [!][@~=]["][!][@~=][^]term[$]...["]
  
• Fixed texforms searches that contain ^ (start of field) and $ (end of field) to use indexes when querying table.
• Changed the default value for the number of records inserted / updated / reindexed before refreshing the screen display from 50 to 500. The loadfreq option may be used to alter the default value.
• Changed texload environment syncing from every 500 records to every 50,000 records. The change improves data loading times.
• Added -U option to texload. The option ensures that only updates are permitted. Insertions and deletions are treated as errors.
• Added -Tnum option to texload. The option is used to restrict the number of records copied from the main data file to the loading file when the -t option is used.
• Fixed issue where truncating a file with multiple partitions does not get picked up by other processes that have the file open.
• Fixed issue with generation of tmpname (temporary file names) after 702 failures to cleanup.
• Fixed problem with timeout of queries when sorting results (via a TexQL order statement).
• Fixed issue where the last matching record is displayed rather than the first when the last record is a false match.

Upgrade Notes

The upgrade from Texpress 8.1 to Texpress 8.2 involves running an upgrade program and performing a database reindex. Please follow the instructions below carefully:

1. Install Texpress 8.2.001 or greater.
   The following steps need to be performed for all  installed databases.
   Please ensure that no-one is using the database while the upgrade is underway.
2. Log in as the database administrator.
3. Enter texupgrade dbname 
   where dbname is the name of the database.
   The upgrade involves a reindex so may take some time. Once the upgrade is complete the database should be reindexed again to provide optimal performance.
4. Enter texadmin dbname
   where dbname is the name of the database.
5. Select Function->Configure from the Admin menu.
6. Note the Capacity of database value and re-enter it over the existing value.
7. Select Function->Save from the Configuration menu.
8. Enter Y to the Changes require index rebuild Continue? question.
9. Enter Y to the Prepare database for an index rebuild? question.
10. Press the space bar at the Database configuration complete message.
11. Select Function->Save from the Configuration menu.
12. Select Maintenance->Rebuild/load/progress from the Admin menu.
13. Select Function->Perform from the Rebuild menu.
14. Press the space bar at the Preparation for rebuild completed message.
15. Press the space bar at the Completed rebuilding the database message.
16. Select Function->Exit from the Admin menu.
17. Return to step 3 to commence upgrading the next database.

The database may be accessed once the upgrade is complete. The new indexing mechanism should produce smaller indexes with improved performance.

Top