The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.
Major new features in this release include:
Roles:
PostgreSQL now supports database roles, which simplify the
management of large numbers of users with complex
overlapping database rights.
IN/OUT Parameters:
PostgreSQL functions now support IN, OUT and INOUT
parameters, which substantially improves support of complex
business logic for J2EE and .NET applications.
Two-Phase Commit (2PC):
Long in demand for WAN applications and heterogeneous data
centers using PostgreSQL, this feature allows
ACID-compliant transactions across widely separated
servers.
Some Performance Enhancements found in this release include:
Improved Multiprocessor (SMP) Performance:
The buffer manager for 8.1 has been enhanced to scale almost
linearly with the number of processors, leading to significant
performance gains on 8-way, 16-way, dual-core, and multi-core
CPU servers.
Bitmap Scan:
Indexes will be dynamically converted to bitmaps in memory when
appropriate, giving up to twenty times faster index performance
on complex queries against very large tables.
Table Partitioning:
The query planner is now able to avoid scanning whole sections
of a large table using a technique known as Constraint
Exclusion.
Shared Row Locking:
PostgreSQL's "better than row-level locking" now supports even
higher levels of concurrency through the addition of shared
row locks for foreign keys.
For a more complete listing of changes in this release, please see the
Release Notes visible at:
http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
With Glom you can design table definitions and the relationships
between them, plus arrange the fields on the screen. You can edit
and search the data in those tables, and specify field values in
terms of other fields. It's as easy as it should be.
The design is loosely based on FileMaker Pro, with the added
advantage of separation between interface and data. Its simple
framework should be enough to implement most database
applications. Without Glom these systems normally consist of lots
of repetitive, unmaintainable code.
Glom-specific data such as the relationship definitions is saved
in the Glom document. Glom re-connects to the database server
when it loads a previous Glom document. The document is in XML
format.
Glom uses the PostgreSQL database backend but it can not edit
databases that it did not create, because it uses only a simple
subset of Postgres functionality.
Submitted by: adamw
PostgreSQL's clients(front ends) and servers(back ends). A PostgreSQL client can
connect to pgpool as if it were a standard PostgreSQL server.
pgpool caches the connection to PostgreSQL server to reduce the overhead to
establish the connection to it.
WWW: http://pgpool.projects.postgresql.org/
PR: 87701
Submitted by: Choe, Cheng-Dae <whitekid@gmail.com>
This is PDO Oracle OCI8 driver for PHP 5. Unlike PDO_ODBC
driver which segfaults when used from apache 2.0, it works.
Tested with Oracle 9 Database Server. It should work with
versions 7, 8 and 10 also.
PR: ports/87197
Submitted by: Simun Mikecin <numisemis@yahoo.com>
SQLite V3 is NOT compatible with the bundled SQLite 2 in PHP 5,
but is a significant step forwards, featuring complete
utf-8 support, native support for blobs, native support for
prepared statements with bound parameters and improved concurrency.
PR: ports/86037
Submitted by: Alexander Zhuravlev <zaa@zaa.pp.ru>
as prepared statements and bound parameters. PDO drivers are dynamically
loadable and may be developed independently from the core, but still accessed
using the same API.
PR: ports/86033
Submitted by: Alexander Zhuravlev <zaa@zaa.pp.ru>
distribution (up to 7.2), but now lives its own life. Naturally, we
should have a port for it :-)
Official information:
Pgeasy is a PostgreSQL API that is a cleaner interface to the libpq
library, more like an SQL 4GL interface.
Approved by: ade, seanc (implicit)
In Rails, the model is handled by what's called a object-relational
mapping layer entitled Active Record. This layer allows you to present
the data from database rows as objects and embellish these data objects
with business logic methods
PR: ports/82397
Submitted by: Jonathan Weiss <jw@innerewut.de>
PR: 37904
Submitted by: Stefan Schmidt <stefan.schmidt (at) stadtbuch.de>
Remark: isql-viewer depends on IBM's version (2.2) of BSF before it has
been donated to the Apache Software Foundation. Therefore this version
still uses the package name "com.ibm.bsf". In the current version of BSF,
the package name has been changed to "org.apache.org" to reflect the new
ownership. Thus, no separate port has been created to install this
dated version of BSF.
remove it;
- replace it by two new ports: databases/jdbc-oracle8i and
databases/jdbc-oracle9i.
Notes:
- databases/jdbc-oracle8i is intended for JDK 1.2 & 1.3, but
it runs fine with JDK 1.4;
- databases/jdbc-oracle9i is intended for JDK 1.4, and it can be
used to access Oracle 8i & 9i databases;
- there is another driver for Oracle 10g, but I have no 10g to
test it; could be added later.
PR: ports/81567
Submitted by: thierry
Repocopied by: marcus
databases through the DBI.
This is a port to provide DBD:Pg driver on FreeBSD
4.x with Perl 5.00505. So if you use Perl 5.6 or
lator, you should use databases/p5-DBD-Pg port.
Requsted by: Jun Watahiki <j-watahiki at ensure.jp>
PEAR::DB_Table builds on PEAR DB to abstract datatypes and automate table
creation, data validation, insert, update, delete, and select; combines
these with PEAR::HTML_QuickForm to automatically generate input forms
that match the table column definitions.
PR: ports/78588
Submitted by: Antonio Carlos Venancio Junior <antonio@php.net>
emulator and provides a uniform, object-based interface for the
Berkeley-style database systems.
PR: ports/78600
Submitted by: Antonio Carlos Venancio Junior <antonio@php.net>
