view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

- Fix what was arguably a bug in the caching/syncing code.
  Previously, one process could update a row and another process could
  then update that same row.  Now the second process will throw an
  exception.

BUG FIXES:

- Accidentally left debugging turned on in Alzabo::Exceptions.

- The schema creator did not allow you to remove a length or precision
  setting for a column once it had been made.

- Require a length for CHAR and VARCHAR columns with MySQL.

- Add error on setting precision for any column that doesn't allow
  them with MySQL.

- The interaction of caching rows and Alzabo::MethodMaker was not
  right.  Basically, it was determined at compile time whether or not
  to use the cached row class but this needs to be determined at run
  time.  This has been fixed.

- Using the Alzabo::Runtime::Row->rows_by_foreign_key method would
  fail when the column in one table did not have the same name as a
  column in the other table.  Reported by Michael Graham (along with a
  correct diagnosis, thanks!).

- Don't specify a database name when creating or dropping a database.
  Reported and patched by Dana Powers.

ENHANCEMENTS:

- Rules violations error messages (bad table name, for example) in the
  schema creator are now handled in a much friendlier manner.  Instead
  of the big error dump exception page it returns you to the page you
  submitted from with an error message.

- Add Alzabo::Create::Column->alter method which allows you to change
  the column type, length, and precision all at once.  This is
  necessary because some of the column type validation code will
  insist that a column have a length setting.  If you try to change
  them in two separate operations it will throw an exception.

- Add Alzabo::ObjectCache::Store::Null - This allows you to use any
  multi-process syncing module without using up the memory that
  Alzabo::ObjectCache::Store::Memory uses.

- Add Alzabo::ObjectCache::Store::BerkeleyDB - I'm not sure if storing
  in a db file is really a performance win (vs. null storage) because
  of the work needed to freeze & thaw the row objects.  Benchmarks are
  needed.

- Add support for fulltext indexes (MySQL).

- Don't show fulltext or column prefix options when creating indexes
  for databases that don't support these features.

- Use cardinality & dependency language for relations.

- Add some style to the schema creator (via stylesheets).  It looks a
  little better now.

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

0.44 May 4, 2001

BUG FIXES:

- Bug fix in Alzabo::Runtime::Table->set_prefetch.  Reported by Bob
  Gustafson.

- Don't try to make directories when running Makefile.PL.  Save it for
  later after user does 'make install'.

- Fix handling of geometric types in Postgres (they were all being
  rejected as invalid).

- Drop columns from a table before adding new ones.  Sometimes this
  makes a difference.  For example, if you are using MySQL and drop an
  existing AUTO_INCREMENT column and add a new one that is also
  AUTO_INCREMENT.

- Only allow one sequenced column per table when using MySQL.

- Doc fixes.  Thanks to Ron Savage for pointing me towards some of
  these.

- Fix a bug with the schema creator.  If you attempted to make a
  change to a column with an extended type and you did not change the
  type, an error occurred.

ENHANCEMENTS:

- Schema creator now shows you a list of possible column types instead
  of having you type it in.  However, for complex types like MySQL's
  ENUM or Postgres' POLYGON there is a text box to type it in.

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

0.43 Apr 25, 2001

ENHANCEMENTS:

- Allow passing of port when executing SQL from schema creator.

- Confirm schema deletion in schema creator.

BUG FIXES:

- Quick hack to fix a problem with Alzabo::MethodMaker when using
  caching.  However, this requires that the caching modules be loaded
  first, before Alzabo::MethodMaker.  A more palatable fix will be in
  a future release.

- Fix a problem with prefetching rows that caused row objects to
  contain undefined values for certain columns.  This only happened if
  you were prefetching one column.

- Fix another problem that left the schema creator still broken.