Browse Prior Art Database

Data binding negotiation in programming languages based on application scenario patterns from the globalization perspectives

IP.com Disclosure Number: IPCOM000014708D
Original Publication Date: 2002-Feb-20
Included in the Prior Art Database: 2003-Jun-20
Document File: 3 page(s) / 65K

Publishing Venue

IBM

Abstract

The disclosed invention is a middleware for programming language binding with database to decide an appropriate data type mapping between different languages without character set mismatch problem at runtime based on an application scenario pattern regarding domestic mono-lingual or global multilingual.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 3

  Data binding negotiation in programming languages based on application scenario patterns from the globalization perspectives

    The disclosed invention is a middleware for programming language binding with
database to decide an appropriate data type mapping between different languages
without character set mismatch problem at runtime based on an application
scenario pattern regarding domestic mono-lingual or global multilingual.
Conventionally, programming language binding has been done based on a fixed
assumption of a particular relation between a data type name and a character set.
However, such a relation between a data type and a character set is often
implementation-defined or runtime environment dependent. This situation is
becoming more obvious in the internationalized environments. For example, a
data type CHAR is always ANSI or ANSI based national language version code pages
in a particular implementation (X). On the other hand, a data type CHAR is
defined as ANSI based monolingual code page in some situations, but Unicode based
multilingual code page in another situations by a different implementation (Y).
This flexibility of the relation between a data type and character set name
depends on requirements of an application design based on the scenario. Today,
under such circumstances, a programming language binding based on a fixed
assumption by only a data type information tends to cause a character set
mismatch problem between a calling programming language module such as C and a
called database interface language SQL. The invention resolves the problem of
loss of character data caused by such character set mismatch in programming
language binding by introducing the information about application scenario
pattern as a new data type binding attribute at runtime.

There is a fixed relation between a data type and its supporting character set
in a particular circumstance. The invention is to make the middleware being
aware of this relation. The relation can be identified by a program coding
that refers to a combination of the following information:
an individual implementation specification of programming language, that is
fixed.

a language or code page attribute, that depends on a runtime platform.

The invention also utilizes the application scenario pattern from
globalization perspectives as an additional factor to the relation between a
data type and its supporting character set to decide the appropriate data type
binding. The scenario pattern is given externally by an application
programmer or a user at application start up time. These avoid pro...