Free sql database maker software for linux

Hello! Thank you for donating your knowledge and time to our cause. Pariahware, Inc. is currently working on a Bible trivia game that is a cross between the TV game show "Who Wants to be a Millionaire?" and the electronic game series "You Dont Know Jack!" As one might imagine, this can be a daunting task.
That is why we are asking for your help in coming up with some GREAT Bible questions in order to make this game even more fun than we could do by ourselves! When you are finished submitting all of your questions, please e-mail the "qanda.rsd" file back to submissions@pariahware.com. By submitting the questions that you come up with, you agree to the following:
The Legal:
1. You expect no royalty fees or other payment for Pariahware, Inc. using your questions in the game.
2. Any parts of the questions you submit may be altered at will by the members of Pariahware, Inc.
3. Even though you submit a question for the game, that does not necessarily mean it will appear in the game.
4. If your name is included in your e-mail, Pariahware, Inc. has the right to add it as an acknowledgement, unless otherwise noted. You will not be paid as a result of having your name listed.
The How To:
1. Make sure that the Got Word DB Maker application and the "qanda.rsd" file are in the same folder or the program will not work.
2. Double-click the Got Word DB Maker application icon.
3. Select the radio button in the lower-left-hand corner that says "Add new question".
4. There are five text fields. The large one on the top is for the question. The other four are for potential answers. All of these need to be filled.
5. The correct answer needs to be selected by the "drop down" in the upper-right-hand corner.
6. The book of the Bible, in which the question is referencing, needs to be selected in the upper-left-hand corner.
7. Below the book selection is value (points) for the question. This needs to be selected as well.
8. When all of this has been done, the "Save New Question" button will activate. Click it to save your question.
Word of Caution:
To make changes to question that you have already entered, click the "edit existing questions" radio button.
Enhancements:
- Bug Fixes.

Mckoi SQL Database is a full featured SQL-92 relational database management system written in Java.

The software can operate as either a dedicated multi-client, multi-threaded database server, or can be used as an embedded database inside a Java application.

The engine is designed to be easy to use and maintain and versatile for sophisticated database development tasks. The software provides a JDBC 2.0 driver.

To use Mckoi SQL Database, you will need a JavaTM runtime environment version 1.2 or greater. Sun provides Java runtimes for Win32, Solaris and Linux from their website at http://www.javasoft.com/j2se/. IBM also provides various Java runtimes for a number of platforms at http://www.ibm.com/java/jdk/download/.

When Java has been installed on your system, unpack the mckoi distribution file to a directory in your file system. Then you are ready to create a database and develop your database application.

Creating A Database

Before you can begin development of your database application, you will need to create and configure a blank database. The database configuration file describes all of the configurable properties of the database (details of the database configuration file are covered in the next section). The software ships with a default configuration that looks for a database at path ./data in your filesystem.

To create a database using the default configuration with an admin username of admin_user and password aupass00, go to a prompt, change to the Mckoi Database distribution directory and type:

java -jar mckoidb.jar -create "admin_user" "aupass00"

We do not advise using either this username or password in a production system. The user created here has full control over every aspect of the database so choose a username / password carefully.

When the command has completed, a sub-directory called data will have been generated. This directory is used to store data from the database. A sub-directory called log is also generated which stores debugging and query log information.

Database Configuration

When you run the mckoidb.jar package, it looks for a file named db.conf in the current directory. This file contains a number of variables that determine where the database looks for information, as well as other user-definable properties. The configuration file can be renamed and copied to a different location. If you change the configuration file location, you must supply the location when you run the database;

java -jar mckoidb.jar -conf [location of conf file] .....

You can edit the configuration file with a text editor. The default configuration file that ships with the software contains extensive comments on what each variable does.

MySQL table patcher is a patch that reads table creation file (tables.sql) and compares it to what mysqldump gives. It creates SQL clauses to update the database to match the creation file.

RPM Package Maker is a frontend for other linux tools in order to help linux users to create RPM packages quickly and easily.
Since version 0.8 minimal spec files are kept in:
/usr/src/packages/SPECS/mini
Enhancements:
- Small improvements and bugfixes

Haskell Database Connectivity project provides an abstraction layer between Haskell programs and SQL relational databases. This lets you write database code once, in Haskell, and have it work with any number of backend SQL databases (MySQL, Oracle, PostgreSQL, ODBC-compliant databases, etc.)
HDBC is modeled loosely on Perls DBI interface http://search.cpan.org/~timb/DBI/DBI.pm, though it has also been influenced by Pythons DB-API v2, JDBC in Java, and HSQL in Haskell.
HDBC is a from-scratch effort. It is not a reimplementation of HSQL, though its purpose is the same.
Main features:
- Ability to use replacable parameters to let one query be executed multiple times (eliminates the need for an escape function)
- Ability to access returned rows by column number
- Ability to read data from the SQL server on-demand rather than reading the entire result set up front
- HUnit testsuite for each backend driver
- Well-defined standard API and easy backend driver implementation
- Lazy reading of the entire result set (think hGetContents, but for the results of SELECT) (see sFetchAllRows)
- Support for translation between Haskell and SQL types
- Support for querying database server properties
- Add-on package (hdbc-missingh) to integrate with MissingH, providing a database backend for AnyDBM.
- Support for querying metadata such as column names.
- Support for querying additional metadata (column types, etc.)

SQL::Schema is a Perl module to convert a data dictionary into SQL statements.

SYNOPSIS

use DBI;

my $dbh = DBI->connect(...);

use SQL::Schema;

my $schema = SQL::Schema->new($dbh);

my $sql = $schema->string;
print $sql;

print "$schema";

WARNING

This is alpha software. It currently works with Oracle databases only. The name of the module might be changed in future releases as well as its interface.

If somebody is modifying the datase schema during the life time of an SQL::Schema object, the object will probably fail and / or produce wrong information.

SQL::Schema is a class for objects representing a database schema. The methods of an instanciated object do allow to access the information within a databases data dictionary and to represent them as SQL create statements and the like using the proper SQL dialect.

Constructor

$schema = SQL::Schema->new($dbh);

The new method instanciates a schema object. The only argument required is a database handle, which has to offer the same API as described within DBI(3).

Methods

$sql = $schema->string;

Returns an SQL string containing several statements at once. This string contains all the SQL statements to create the database schema.

This method is overloaded with the string operator. So the following two lines are equivalent:

$sql = $schema->string;
$sql = "$schema";

SQLite is a small C library that implements a self-contained, embeddable, zero-configuration SQL database engine.
Main features:
- Transactions are atomic, consistent, isolated, and durable (ACID) even after system crashes and power failures.
- Zero-configuration - no setup or administration needed.
- Implements most of SQL92. (Features not supported)
- A complete database is stored in a single disk file.
- Database files can be freely shared between machines with different byte orders.
- Supports databases up to 2 terabytes (241 bytes) in size.
- Sizes of strings and BLOBs limited only by available memory.
- Small code footprint: less than 30K lines of C code, less than 250KB code space (gcc on 486)
- Faster than popular client/server database engines for most common operations.
- Simple, easy to use API.
- TCL bindings included. Bindings for many other languages available separately.
- Well-commented source code with over 95% test coverage.
- Self-contained: no external dependencies.
- Sources are in the public domain. Use for any purpose.
The SQLite distribution comes with a standalone command-line access program (sqlite) that can be used to administer an SQLite database and which serves as an example of how to use the SQLite library.
Create A New Database:
- At a shell or DOS prompt, enter: "sqlite3 test.db". This will create a new database named "test.db". (You can use a different name if you like.)
- Enter SQL commands at the prompt to create and populate the new database.
Write Programs That Use SQLite
Below is a simple TCL program that demonstrates how to use the TCL interface to SQLite. The program executes the SQL statements given as the second argument on the database defined by the first argument. The commands to watch for are the sqlite3 command on line 7 which opens an SQLite database and creates a new TCL command named "db" to access that database, the invocation of the db command on line 8 to execute SQL commands against the database, and the closing of the database connection on the last line of the script.
#!/usr/bin/tclsh
if {$argc!=2} {
puts stderr "Usage: %s DATABASE SQL-STATEMENT"
exit 1
}
load /usr/lib/tclsqlite3.so Sqlite3
sqlite3 db [lindex $argv 0]
db eval [lindex $argv 1] x {
foreach v $x(*) {
puts "$v = $x($v)"
}
puts ""
}
db close

Firebird is a relational database offering many ANSI SQL-99 features that runs on Linux, Windows, and a variety of Unix platforms.

Firebird offers excellent concurrency, high performance, and powerful language support for stored procedures and triggers. Firebird Relational Database has been used in production systems and under a variety of names since 1981.

Firebird is a commercially independent project of C and C++ programmers, technical advisors and supporters developing and enhancing a multi-platform relational database management system based on the source code released by Inprise Corp (now known as Borland Software Corp) on 25 July, 2000 under the InterBase Public License v.1.0.


New code modules added to Firebird are licensed under the Initial Developers Public License. (IDPL). The original modules released by Inprise are licensed under the InterBase Public License v.1.0. Both licences are modified versions of the Mozilla Public License v.1.1.

Installing:

In order to install the firebird version of IB 6.0 you will need to perform the following steps:

1. Get the required packages:

Get the glibc update from RedHat, the one I used
was from ftp://updates.redhat.com/7.0/i386/glibc-2.2-5.i386.rpm

Get ncurses4 from
ftp://carrier.ision.net/pub/ftp.redhat.com/i386/en/RedHat/RPMS/ncurses4-5.0-2.i386.rpm
or another redhat mirror.

Get Firebird from
ftp://firebird.sourceforge.net/pub/firebird/release/FirebirdSS-0.9-1.i386.rpm

2. Prepare the installation:

Log in as root.
Use a plain text console to do this and be sure
that all Gnome desktops are closed.
(One user reported that the Gnome desktop
(apparently ICEwm)
blocked port 3050. I could not reproduce this
here, but it seems that it uses port numbers
that arent assigned in /etc/services for own
purposes)

3. Add localhost.localdomain to /etc/hosts.equiv:
echo localhost.localdomain >>/etc/hosts.equiv

4. Change to the directory where you have placed
the downloaded packages.

5. Install the glibc update:
rpm --install --force glibc-2.2-5.i386.rpm

6. Install libncurses.so.4:
rpm --install --force ncurses4-5.0-2.i386.rpm

7. Install Firebird:
rpm --install --force FirebirdSS-0.9-1.i386.rpm

8. Add /opt/interbase/bin to your path:
You can either change /etc/profile
or do
export PATH=$PATH: /opt/interbase/bin
or
change the profiles in your users home directories

9. Check that all went well:

Read /opt/interbase/SYSDBA.password
to get your SYSDBA password.

gsec -display
should display the list of known users
(SYSDBA only after a fresh install)

isql /opt/interbase/examples/employee.gdb
SQL> SHOW TABLES;
should display all tables from this database
SQL>quit;