Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc.  objects to represent your data model. Alzabo is also capable
of reverse engineering your data model from an existing system.

Its second function is as an RDBMS to object mapping system. Once you have
created a schema, you can use the Alzabo::Runtime::Table and
Alzabo::Runtime::Row classes to access its data. These classes offer a
high level interface to common operations such as SQL SELECT, INSERT,
DELETE, and UPDATE commands.

Please see http://alzabo.sourceforge.net/ for more info.  You can also
install Alzabo via CPAN.


0.64

ENHANCEMENTS:

- Added potentially useful script, alzabo_to_ascii, in eg/ dir.

- Ask for port when setting up tests.

- Turn on stacktraces for all Alzabo::Exception objects.

- Removed the deprecated "lookup_tables" option from
Alzabo::MethodMaker.

- Removed the deprecated next_row methods from the various cursor
classes.

- Removed the deprecated Alzabo::Runtime::Table->func method.

- Major changes to how joins are done.  It is now possible to mix
together various sorts of outer joins in a single query.  In addition,
it is now possible to specify a foreign key that should be used when
joining two tables.

- The "tables" parameter has been renamed as "join".

- The Alzabo::Create::Schema->right_outer_join and
Alzabo::Create::Schema->left_outer_join methods have been removed.
Use the ->join method instead, which can now be used to do outer joins
as well, via:

  $schema->join( join => [ left_outer_join => $foo, $bar ], ... )

- The functionality of Alzabo::Runtime::OuterJoinCursor has been
merged into Alzabo::Runtime::JoinCursor.

- Alzabo::Exception::Driver->bind now returns an array reference, not
an array.

BUG FIXES:

- Fix failure to load schema objects from file when $\ is set to
something like "\n".  Reported by Brad Bowman.

- Fixed Postgres reverse engineering to work with slightly changed
system tables in 7.2.

- Fix handling of table alterations for postgres.  Temp tables were
being created but not dropped and the data saved in the temp table was
not being restored to the real table.  Also, Alzabo was trying to
create sequences again when altering tables Based mostly on a patch
from Daniel Gaspani.

- Fix handling of primary key changes for Postgres (I'm still not sure
it's entirely correct).

- Fix detection of primary key changes for schema diffs.

- Handle NOT IN for where conditions.




Reply via email to