README for HP Neoview Release 2.4

The Release 2.4 HPDM features are:

• Database-Object Browsing

— Provides database-object browsing capabilities (these capabilities also exist in the DB

Admin product)

— Displays partition information for individual Neoview SQL objects

— Displays a partition summary for groups of objects (for example, all tables in a schema)

— Displays the schema size

— Displays sequence numbers in table columns

— Provides a DDL tool to generate and save the DDL script for a group of Neoview SQL

objects

— Displays table profile and statistics information

— Generates and displays system status messages

• SQL Whiteboard

— Executes DDL/DML statements

— Persists queries across sessions for reuse

— Exports query results to a spreadsheet

— Allows a portion of an SQL statement to be highlighted and executed (syntax

highlighting)

— Cancels an executing query

— Opens/saves query text to a file

• HPDM Framework

— Provides connection management for widgets

— Supports persistence for widget and application data

— Includes menu management

— Implements area management (hide, show, and deploy)

— Exports grid contents to a spreadsheet

— Manages options for an HPDM application as a whole and for individual areas and

widgets

— Modifies and tests HPDM framework and widgets to support the Vista security model

(includes code-signing)

— Launches the Neoview Command Interface (NCI)

— Supports character sets for ISO, SJIS, and Unicode based on a single-client locale

For more information about using the HP Database Manager, see the HPDM online help that

installs with the product.

Neoview Character Sets

In Release 2.4, the Neoview Character Sets product contains these enhancements:

• Character string functions now treat each multibyte character in an input string as one

character, regardless of the byte length of the character.

• In SJIS and Unicode configurations, the LIKE predicate now handles an underscore as one

character, regardless of how a character is stored in the database, and now compares character

strings at the character level, not the byte level.

• Syntax error messages now identify the number of characters from the start of the SQL

statement where the error occurred, allowing you to find an invalid character more quickly

with your editor.

• You can now translate a string from UCS2 to UTF8 (and from UTF8 to UCS2) in the Unicode

configuration, and you can translate a string from SJIS to UCS2 (and from UCS2 to SJIS) in

the SJIS configuration.