IQL: A Graphical Interface for Full SQL Queries

  • Hugo B. Ramos
Conference paper


IQL (Interactive Query Language) provides interactive formulation and optimization of relational queries. IQL’s query interface supports fast and easy formulation of full SQL queries by using a novel object-oriented representation of query concepts. A query is a graph made up of a set of tree-like expressions (predicates, arithmetic and boolean expressions) specified at different graphic levels on subsets of relations of a database schema. The power and flexibility of query graphs derive from the independent metamodelization of implied formalisms, so complex queries may be expressed graphically in their entirety. Querying performances are improved in several ways: syntax and consistency issues are permanently verified during query formulation, a variety of abstraction mechanisms like the denomination of queries (or expressions) and the use of parameters, permit modular and generic reusability, even on different database schemas, and query optimization mechanisms are used to generate compiled versions of less-cost equivalent queries in relation to a given operational context (i. e., logic access and data schémas). IQL has been implemented as a part of an integrated environment for the design of databases using Graphtalk™, the object-oriented graph-based development tool from Rank Xerox.


Query Language Database Schema Access Schema Execution Plan Query Optimization 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    Angelaccio, M., Catarci, T., Santucci, G. Qbd*: A Graphical Query Language with Recursion. IEEE Transactions on Software Engineering 16, 2 (October 1990), 1150–1163.CrossRefGoogle Scholar
  2. [2]
    Auddino, A., Dennebouy, Y., Dupont, Y., Fontana, E., Spaccapietra, S., Tari, Z. Super: A Comprehensive Approach to DBMS Visual User Interfaces. 1er Séminaire sur les Bases de Données-CERIST (June 1991), Alger, 341-364.Google Scholar
  3. [3]
    Boksenbaum, C. Critique des langages d’interrogation et des langages orienté-objet. Notes des cours, Ecole d’Automne de l’AFCET (November 1990), Port Barcarés, France.Google Scholar
  4. [4]
    Carbonell, N., Pierrel, J. M. Vers un dialogue naturel homme-machine. Colloque sur l’Ingénierie des Interfaces Homme-Machine (1989), Sophia-Antipolis, 221-234.Google Scholar
  5. [5]
    Chamberlin, D. D., Boyce, R. F. Sequel: A structured english query language. Proceedings of the ACM-SIGMOD Workshop on Data Description, Access and Control (1974).Google Scholar
  6. [6]
    Chamberlin, D.D., Astrahan, M.M., King, W.F., Lorie, R.A., Mehl, J.W., Price, T.G., Schkolnick, M., Selinger, P.G., Slutz, D.R., Wade, B.W., Yost, R.A. Support for repetitive transactions and ad hoc queries in System R. ACM Transactions on Database Systems 6, 1 (March 1981), 7–94.MathSciNetCrossRefGoogle Scholar
  7. [7]
    Coutaz, J. The construction of User Interface and the Object Oriented Paradigm. Proceedings of ECOOP’87 (June 1987), 135-144.Google Scholar
  8. [8]
    Coutaz, J. Interfaces Homme-Ordinateur, Conception et Réalisation. DUNOD Informatique (June 1990). BORDAS, Paris, 135–144.Google Scholar
  9. [9]
    Date, C. J., Hopewell, P. File definition and logical data independance. Proceedings of the AC-SIGFIDET Workshop on data description acces and control 16, 12 (June 1971).Google Scholar
  10. [10]
    Dayal, U. On Nest and Trees: A Unified Approach to Processing Queries That Contain Nested Subqueries, Aggregates, and Quantifiers. Proceedings of the 13th VLDB Conference (1987), Brighton, 197-208.Google Scholar
  11. [11]
    Ficher, G. Human Computer Interactions Software: Lessons Learned, Challenges Ahead. IEEE Software 6, 1 (1989), 44–52.CrossRefGoogle Scholar
  12. [12]
    Finkelstein, S., Schkolnick, M., Tiberio, P. Physical Database Design for Relational Daubas es. ACM Transactions on Database Systems 13, 1 (1988), 91–128.CrossRefGoogle Scholar
  13. [13]
    Fogg, D. Lessons from Living in a Database graphical query interface. Proceedings of the 1984 SIGMOD Conference (1984), Boston, 100-106.Google Scholar
  14. [14]
    Held, G. D., Stonebraker, M. R., Wong, E. Ingres: A Relational Database System. Proceedings of the National Computer Conference (May 1975), 409-416.Google Scholar
  15. [15]
    Ibm Corp. IBM Database 2 Application Design and Tuning Guide (GG24-3004). International Technical Support Center (March 1986).Google Scholar
  16. [16]
    Ibm Corp. Database 2 General Information Manual. IBM Corporation (1987), White Plains, NY, 30p.Google Scholar
  17. [17]
    Ansi Ansi-Sql-2 Standard (1988). J. Melton.Google Scholar
  18. [18]
    Jarke, M., Koch, J. Query Optimization in Database Systems. Computing Surveys 16, 2 (June 1984).Google Scholar
  19. [19]
    Jeulin, P., Khlat, M., Wllhem, L. Graphtalk, GQL et Gknowledge: des techniques d’intelligence artificielle au service d’un environnement de génie logiciel. Actes du Congrès INFORSID 88 (7–10 June 1988), La Rochelle, 519-561.Google Scholar
  20. [20]
    Khlat, M., Jeulin, P. Graphtalk Reference Manual (1987). Rank Xerox.Google Scholar
  21. [21]
    Kim, W. On Optimizing an SQL-like Nested Query. ACM Transactions on Database Systems 7, 3 (September 1982), 443–469.MATHCrossRefGoogle Scholar
  22. [22]
    King, R., Melville, S. Ski: A Semantics-Knowledgeable Interface. Proceedings of 10th International Conference on VLDB (1984), Singapore, 115-123.Google Scholar
  23. [23]
    King, P., Poulovassilis, A. Fdl: A language which integrates Database and Functional Programming. INFORSID88 (June 1988), La Rochelle, 167-181.Google Scholar
  24. [24]
    Kuntz, M., Melchert, R. Pasta-3’s Graphical Query Language: Direct Manipulation, Cooperative queries. Full Expressive Power. Proceedings of 15th International Conference on VLDB (August 1989). VLDB Endowment, Amsterdam, 97–105.Google Scholar
  25. [25]
    Lecluse, C., Richard, Ph. Langages orienté-objet et bases de données: l’expérience 02. Proceedings BD3 (1989), Genève, 155-168.Google Scholar
  26. [26]
    McDonald, N., Stonebraker, M. R. Cupid: A User friendly Graphics Query Language. Proceedings of the AC-PACIFIC (April 1975), San Francisco, CA., 127-131.Google Scholar
  27. [27]
    McDonald, N. Cupid: A graphics oriented facility for support of non-programmer interactions with a database. Memorandum n° ERL-M563 (November 1975), UCLA, San Francisco, CA., 171p.Google Scholar
  28. [28]
    Nanard, J. La Manipulation Directe en Interface Homme-Machine. Thèse de Docteur d’Etat (December 1990), USTL, Montpellier, France.Google Scholar
  29. [29]
    Oracle France Performances Oracle. ORACLE France (1987), Paris.Google Scholar
  30. [30]
    Ramos, H. B. Iql: Langage Interactif de Génération et Optimisation de Requêtes, Interface de Spécification et Optimisation. Rapport interne (June 1990), LIRMM, Montpellier, France, 80p.Google Scholar
  31. [31]
    Ramos, H. B. Iql: Interface Graphique Paramétrable pour requêtes relationnelles. 1st Seminar on Data Bases (June 1991), Alger, 365-385.Google Scholar
  32. [32]
    Rank Xerox Atelier Merise. Graphtalk 1.2 Release (December 1988).Google Scholar
  33. [33]
    Rowe, L. A., Danzig, P., Choi, W. A visual shell interface to a database. Software, Practice and Experience 19, 6 (June 1989), 515–528.Google Scholar
  34. [34]
    Selinger, P. G., Astrahan, M. M., Chamberlin, D. D., Lorie, R. A., Price, T. G. Accès Path Selection in a Relational Database Management System. Proceedings of the AC-SIGMOD International Conference on Management of Data (May 1979), Boston, Mass., 23-34.Google Scholar
  35. [35]
    Sellis, T., Ghosh, S. On the Multiple-Query Optimization Problem. IEEE Transactions on Knowledge and Data Engineering 2, 2 (June 1990).Google Scholar
  36. [36]
    Shneiderman B. Direct manipulation, a step beyond programming languages. IEEE Computer 16, 8 (1983).Google Scholar
  37. [37]
    Shneiderman B. Designing the User Interface, Strategies for effective human-computer interaction. Addison-Wesley (1987).Google Scholar
  38. [38]
    Stonebraker, M., Wong, E., Kreps, P., Held, G. The design and implementation of INGRES. Communications of the ACM Transactions on Database Systems 1, 3 (September 1976), 189–222.CrossRefGoogle Scholar
  39. [39]
    Stonebraker, M., Kalash, J. Timber: A sophisticated relation browser. Proceedings of 8lh Conference on Very Large Databases, (1982), 1-10.Google Scholar
  40. [40]
    Ullman, J. D. Principles of Database and Knowledge-Base Systems 1 (1988). Computer Science Press, Y. Vassiliou, Ed Ablex, Norwood, N. J.Google Scholar
  41. [41]
    Vassiliou Y., Jarke, M. Query Languages-A taxonomy. Human Factors and Interactive Computer Systems (1984). Y. Vassiliou, Ed. Ablex, Norwood, N. J.Google Scholar
  42. [42]
    Wegner, P. Concepts and Paradigms of Object-Oriented Programming. OOPS MESSENGER 1, 1 (August 1990), 7–87.CrossRefGoogle Scholar
  43. [43]
    Weiss, H. M. The ORACLE Database Management System. Mini-micro Systems (August 1980), 111-114.Google Scholar
  44. [44]
    Wong, H. K. T., Kuo, I. Guide: A Graphical User Interface for Database Exploration. Proceedings of the 8th International Conference on VLDB (1982), Mexico City, 22-32.Google Scholar
  45. [45]
    Wu, C.T. Implementation of Visual Database Interface using an Object-Oriented Language. IFIP 1989 (1989), 105-125.Google Scholar
  46. [46]
    Xerox Corp. Interlisp-D Reference Manual, Volumes I–III: Language 3101272, 3101273, 3101274 (October 1985).Google Scholar
  47. [47]
    Youssefi, K., Wong, E. Query Processing in a Relational Database Management System. Proceedings of the 5th International Conference on Very Large Data Bases 3, 5 (October 1979). IEEE, New York, 409–417.CrossRefGoogle Scholar
  48. [48]
    Zloof, M. Query-by-Exemple: A Database Language. IBM Systems Journal 16 (1977), 324–343.CrossRefGoogle Scholar

Copyright information

© Springer-Verlag/Wien 1992

Authors and Affiliations

  • Hugo B. Ramos
    • 1
  1. 1.LIRMM, Université de Montpellier IIMontpellierFrance

Personalised recommendations