1. INTRODUCTION & OBJECTIVES
Database
Interface is an industry-standard tool for application development. Using
Database Interface, developers can interact with any back end software (i.e.
Oracle, MS-SQL Server, MS-Access, My-SQL etc).
The database interface can be used to build, test, and debug PL/SQL
packages, procedures, triggers, and functions. Database Interface users can
create and edit database objects such as tables, views, indexes, constraints,
and users. Database Interface's SQL
Editor provides an easy and efficient way to write and test scripts and
queries, and its powerful data grids provide an easy way to view and edit data
related to any DBMS/RDBMS tool.
The requirements of a database
application developer will vary from project to project. On a large team where DBAs manage the DDL, a developer may spend 90% of development
time coding and testing SELECT queries to issue from 3GL or 4GL application
code. In such an environment, a developer might be concerned only with viewing the DDL and database code.
On smaller teams, a developer might be responsible for maintenance of the
development schema, movement of test data between schemas, writing procedure
code, populating tables from legacy sources, and more. Database Interface
facilitates all of these needs.
For example if you are working with oracle, you don't have
to be a PL/SQL expert to access database objects with Database Interface. You
can view the Oracle Dictionary, tables, indexes, stored procedures, and more - all through a
multi-tabbed browser. Database Interface utilizes direct Oracle OCI calls for
full access to the Oracle API.
Advanced editing features save time and increase
productivity. Code can be created from shortcuts and code templates. You can
even create your own code templates.
Use Database Interface to
· Create, browse, or alter objects (tables, views, indexes, etc.)
including Oracle8 TYPE objects
· Graphically build, execute, and tune queries
· Edit and Debug PL/SQL and profile "stored procedures"
including functions, packages, and triggers
· Search for objects
· Find and fix database problems with constraints, triggers,
extents, indexes, and grants
Project
Advantages:
·
Flexibility.
The end-user should be able to use any major commercial (or open-source)
database on the market. Moreover, the end-user should be able to customize the
look-and-feel of the front-end; this includes the ability to internationalize
the application.
·
Maintenance.
Both external documentation (like this) and inline java docs should explain how
things work. I've tried to write clean Java code so that developers who build
on database interface will have a clear, easily extensible starting point.
·
Ease
of Use. Installation is simple; you just have to
create a .war file and drop it in the right directory/folder. The Java search
engine interface is text-based, and intended to provide easy access to search
operations.
IDENTIFICATION OF NEED
To clearly identify the need of this
application, I will try to exemplify one situation.
A project manager is dealing with an
enterprise application, which is in the development phase. This application has
got different faces such as a desktop interface, a web interface and mobile
interface. Initially all these applications are not integrated. Once these
entire interfaces are working well, they are going to be integrated. In such
occasion the database which is being used must be same. But while designing these individual modules,
creating a sample database for each module and perform the test, it is not
possible practically. So for that reason, there must be a kind of tool, using
which we can carry the database to any another location and use the database
there very easily.
The present application will fulfill
the requirement. The current application can be used just as a brief case of
database.
Module
Description
The present application can be differentiated
into the following modules, which are closely integrated with one another.
1.
Structure: It gives the list of all tables which
are present in the current/selected user. This module is used to browse and
view the structure of an existing database object.
2.
Properties: The properties module enables us to
modify data types, size and constraints assigned to each field.
3.
SQL: Using this module, we can use and implement
different kinds of SQL statements. The result of the SQL statement will be
displayed immediately after executing the statement.
4.
Import: This module gives an exclusive feature
of importing the existing SQL scripts to the existing schema.
5.
Export: This module gives the feature of
exporting existing schema object(s) to an SQL file. Here the facility is there
to export only tables, only single user or the entire schema.
6.
Operations: This module will be used to create
new database objects.
7.
Search: Search module provides searching facilities
for searching for the given column names, data or both options.
SOFTWARE AND HARDWARE SPECIFICATIONS
The
following hardware using for developing the project
(i) Hardware
requirement for developing
1. Pentium IV
2. 256 RAM
3. 40 GB HDD
(ii)
Software requirement for developing
1. Windows 2000 Operating system
2. J2SE 1.4
3. Tomcat Web Server 5.0.25
4. Any Database
