rather than always forcing immediate full database inconsistency without completing recovery. Tables get marked logically and/or physically inconsistent. At end, DB is NOT marked inconsistent if all bad tables had save-until dates (see PSEUDOTEMPORARY).

Tables which are not sync'ed and permit failure during crash recovery without any db inconsistency.

Useful for managing large GTT's, or for inducing partition-compatible joins or aggs with other large tables.

Extract that part of "modify to patch_table" that detects the FHDR so that it can be run separately. Intent is for relfhdr fixup after replacing a table file with (e.g.) a backup.

The main thing here is to change createdb to create catalog bitmaps as BYTE(n) instead of a series of named integer columns, makes it much much easier to vary the column max.

Operates at the DI level, largely invisible to higher layers except for syntax and page-compression catalog bits.

Any update to a change-tracked table causes its iirelation.relqid2 to be incremented at commit time. (Partition specific.) An external process can track and compare relqid2's to identify specific tables and/or partitions that changed.

To find out more, please view our web site, check out our FEQ, visit us in the #ingres IRC channel, and talk with us to let us know the kinds of things you want to see in a best in class Open Source RDBMS.

A framework is being developed to execute a set of chosen executables and libraries in order to gather as much useful information as possible for debugging errors, while remaining as open and extensible as possible.

To find out more, please view our web site, join our mailing list, visit us in the #ingres IRC channel, and talk with us to try out these new capabilities.

This project will extend the capabilities of version 1.0.

 var q = from p in db.Products             
         where p.ProductName == "Pen"  
         select p.ProductID;  

This Community Project aims to contribute an Ingres Plugin for the DbLinq project, an alternative implementation of Microsoft Linq.

• Ingres 9.2
• Apache 2.2.8
• PHP 5.2.9

Plus other tools like the Ingres Developer Workbench V0.1 and the Scite editor version 1.77

Revise the Ruby on Rails adapter for ActiveRecord 2.1

Add support for SQL/ANSI Date data types

Allow the Ruby driver to make more than one active connection at any one time. Currently the driver can only have a single connection open.

Provide a mechanism to adjust the default date format for INGRESDATE to VARCHAR conversions

Ruby has a documentation tool, like javadoc, which can be used to document modules, including C code. This project would review the current state of the documentation for the Ruby driver and update it to something more usable and current.

Fix bug #555

Ingres 9.1 onwards can pre-determine the target column type for a parametrized query allowing for improved conversion between Ruby and Ingres data types.

Create a RubyGem package for simplified installation. A part of this project would look at publishing the generated gem on http://rubyforge.org.

Update the Ruby on Rails adapter to support Rails 3.0 and Arel

Add the ability to execute row producing procedures

Update the Ruby GTK demo

COPYDB and UNLOADDB can be used to generate portable (ascii) data files from an existing database which can then be reloaded into a new database. A mechanism is required to enable these utilities to generate UTF8 data files to provide safe transfer of international characters that are not part of the ascii character set.

The Ingres Database Workbench (IDW) is a powerful, low-overhead tool that makes Ingres database development faster and easier and simplifies day-to-day database tasks. IDW allows you to browse your database objects such as tables, views, procedures and rules. You can also issue SQL statements using the SQL scrapbook editor, edit the contents of your tables and edit your procedures and rules. The general purpose SQL editor maintains a command and result set history and includes SQL statement generation tools to help you create correct SQL statements that produce the result sets you need. Based on the Eclipse Rich Client Platform (RCP), IDW easily integrates into your existing architecture. This project will extend the capabilities of version 1.0.

The Ingres Eclipse DTP plug-in provides the ability to develop applications that interface with your Ingres databases from within the Eclipse IDE. You can browse tables and triggers (also known as rules in Ingres), procedures, sequences, synonyms and views. You can edit procedure, table and trigger contents directly with dedicated editors and DTP includes an Ad Hoc SQL editor for ultimate flexibility. You can develop and test Java applications that use the Ingres JDBC driver. DTP allows you to set up database connections locally or in the cloud!

The Ingres Migration Tool Set is a collection of tools and libraries, designed to simplify the task of migrating database schemas and procedures from competitor database products to Ingres Classic and Ingres VectorWise.

The Ingres Development Stack for JBoss creates a rich environment where Java developers can build data-centric applications. Combining the benefits of open source and open standards, the Ingres Development Stack for JBoss allows developers to quickly build portable, reliable, mission critical applications that can scale from the desktop to the enterprise data center.