Extending Relational Data Access Programming Libraries for Fuzziness: The fJDBC Framework

Abstract

Abstract. Fuzzy relational databases have been extensively studied in recent years, resulting in several models and constructs, some of which are implemented as software layers on top of diverse existing database systems. Fuzzy extensions to query languages and end-user query interfaces have also been developed, but the design of programming interfaces has not been properly addressed. In this paper, we describe a software framework called fJdbc that extends the Java Database Connectivity API by allowing fuzzy queries on existing relational databases, using externally-stored metadata. Since the main design objective of this extension is usability for existing database programmers, only a restricted subset of extensions (supported also by an extended object modelling notation) has been included. The overall design of the framework and some experimental data are also described.

Introducing fuzziness in object models and database interfaces through aspects

“…Imperfection in information should be addressed early in the life cycle due to the specifics of uncertainty and imprecision in conceptual modeling 23 and its impact on architectural and implementation decisions, most notably in persistence and querying. 4 Information imperfection is a logical "matter of interest," according to COSMOS 18 terminology.…”

Fuzzy Group Models for Adaptation in Cooperative Information Retrieval Contexts

“…The fJDBC framework described in [20] was used for the logical database design derived from the conceptual model described above. This model provides direct support for the representation of fuzzy generalization relationships, fuzzy classes and fuzzy associations, and enables direct querying from JDBC 4 -like code.…”

“…The adaptation is performed using fJDBC queries which are syntactically SQL sentences that are translated internally to compute the degrees of membership to fuzzy notions. For example, a query to retrieve the (fuzzy) subset of active users is as simple as SELECT * FROM ACTIVE USERS, and the definition of the ACTIVE USERS table is done as described in [20]:…”