view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

  (perldoc Alzabo).

- Added section on optimizing memory usage to Alzabo::FAQ.

- Alzabo::Runtime::Schema->join now takes a parameter called
  'distinct'.  This is useful in situations where you are joining
  between several tables but don't want rows back from all of them.
  In that case, it is possible that you could end up getting more
  duplicates than you need.  This parameter can help you eliminate
  those.

- Add the following Alzabo::Schema methods: begin_work, rollback,
  commit, run_in_transaction.

- If you have GraphViz installed the schema creator can now use it to
  show you a graph of your schema.

BUG FIXES:

- Fix handling of binary attribute for MySQL columns.  Generated SQL
  for creating/altering these columns may have been invalid
  previously.

- The rules were not catching an attempt to create a CHAR/VARCHAR
  column with no length (MySQL).

- Fixed bug that caused limit to not work when there was a where
  clause or order_by clause.  Reported by Ilya Martynov.

- Documented row_column option for MethodMaker.

- order_by was ignored when given to the Alzabo::Runtime::Schema->join
  method.  Reported by Martin Ertl.

- When viewing an existing column in the schema creator, the three
  checkboxes at the bottom were always unchecked.

- The test suite has been revamped to use Test::More.  In the process
  some new tests were added and some (gulp) false positives were
  caught.

- The default column value wasn't being escaped in the schema creator.

DEPRECATIONS

- The Alzabo::MethodMaker option 'lookup_tables' has been deprecated.
  Use the new 'lookup_columns' option instead.

INCOMPATIBILITIES:

- Alzabo::ObjectCache::Store modules now expect an object id instead
  of an object for their delete_from_cache method.

- If you specify give the 'all' parameter to MethodMaker,
  'lookup_tables' is no longer included.

---------------------------------------------------------------------------

0.56

Had to become 0.57 cause I was too hasty in uploading to CPAN.  Doh!

---------------------------------------------------------------------------

0.55 Sep 24, 2001

UPGRADE INSTRUCTIONS:

Because of changes to the internal data structures for some objects,
the saved schema files from older versions of Alzabo will no longer
work with this new version.

In the eg/ directory of this distribution, there is a script called
convert.pl that can be used to convert your schemas.

It is _crucial_ that this script be run while you still have your
_current_ version of Alzabo installed.

To repeat, DO NOT INSTALL THE NEWEST VERSION OF Alzabo BEFORE RUNNING
THIS SCRIPT!

Now that we've got that straightened out...

What this script does is read an existing schema and generate code
that you can run after installing the new version of Alzabo.  This
code will recreate your schema from scratch.

It should be noted that this script _will_ reverse the cardinalities
of the relationships in your schema.  See the entries in BUG FIXES
about this.

If you don't like this and want it the old broken way, you can run the
reverse_cardinality.pl script in the eg/ directory on your schemas.
However, you can only do this _after_ installing this new version of
Alzabo.

So the steps you should take are:

1. Backup all of your schema files (by default, these are stored under
   /usr/local/alzabo).

2. Run convert.pl against each schema you have created by doing:

     perl convert.pl <schema name>

   This will create a file named <schema name>_schema.pl

3. After doing this for _all_ of your schemas, install this version
   Alzabo.

4. Simply run each file created by the convert.pl script.  This will
   overwrite the old schema files.

If you are creating your schemas via a script, then you can use the
code generated by convert.pl to replace the code that does this.  Do
note that the cardinalities will be reversed in the generated code.
Those who are doing this will notice that the generated code seems to
contain everything twice.  This has to do with how Alzabo keeps track
of changes from one generation of a schema to the next.  Simply use
the code up to right before the generated code contains the comment
"Previous generation of schema".