view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

  was doing. RT Ticket #17942.

- Fix bug in reverse engineering function indexes in Postgres.  The
  reverse engineering code always ended up thinking all of the columns
  in the table were used in the index.

- Fix failing MySQL test in 03-runtime.t.  The problem was the test,
  not the Alzabo core.  Reported by Alex McLintock.

- Fixed adding too many "=cut" directives in docs generated by
  Alzabo::MethodMaker.

- Fixed SQL generation for the Postgres functions CURRENT_DATE,
  CURRENT_TIME, and CURRENT_TIMESTAMP, which should not have
  parentheses after them.

- Documented that DATE_TRUNC() is a support Pg function in
  Alzabo::SQLMaker::PostgreSQL. RT Ticket #13843.


0.87  May 14, 2005

BUG FIXES:

- Table names in CREATE INDEX statements for Postgres were not quoted.

- Database names in CREATE/DROP DATABASE statements for Postgres were
  not quoted.

- Postgres database names with upper case characters were never being
  detected as being instantiated, which meant Alzabo always tried to
  recreate the schema from scratch.

- ALTER TABLE statements for Postgres left the table name unquoted
  when renaming a column.

- Even if Alzabo::Runtime::Schema->referential_integrity was false,
  Alzabo was still doing referential integrity checking on inserts.
  Reported by Michal Jurosz.

- 19-schema-name.t did not use the user-supplied connection parameters
  and could fail because of this.  Reported by Daniel Puro.

- Handle quotes in table names returned by Postgres when reverse
  engineering.

- Reverse engineering a Postgres schema that contained indexes on
  functions could fail because the Alzabo::RDBMSRules::PostgreSQL code
  used a function from Text::Balanced without loading it first (or
  making it a prereq for the distro).  Reported by an anonymous user
  via rt.cpan.org.

- When getting the next sequence number from a Postgres schema, Alzabo
  was not quoting the sequence name even if the schema's
  quote_identifiers attribute was true.  Reported by "Martin" via
  rt.cpan.org.

ENHANCEMENTS:

- Allow any key starting with "pg_" when connecting a Postgres
  database.  This allows you to pass attributes like "pg_enable_utf8"
  or "pg_bool_tf".  Prompted by a discussion with Boris Shomodjvarac.


0.86  December 22, 2004

BUG FIXES:

- Allow a UNIQUE constraint as a column attribute for MySQL.

ENHANCEMENTS:

- It is now possible to use a single Alzabo schema object to create
  and access multiple copies of that schema in an RDBMS.  This is done
  by setting the "schema_name" parameter whenever calling a method
  that accesses the RDBMS.

  This feature has a bad interaction with the way internal schema
  diffs are generated, however.  Please see the "MULTIPLE COPIES OF
  THE SAME SCHEMA" section in Alzabo::Intro for details.

- The Alzabo::Runtime::Row->update() method now returns a boolean
  indicating whether any changes were actually made.  Patch by Eric
  Waters.


0.85  October 12, 2004

BUG FIXES:

- The DECIMAL and NUMERIC column types in MySQL were not being treated
  as numeric types.  This meant that you couldn't give such a column
  the UNSIGNED attribute, among other problems.  Reported by Bob
  Sidebotham.

- If a column had CHECK constraints, the Postgres reverse engineering
  failed.  Reported by Ken Miller, fixed by Joshua Jore.

- Insert handles did not include sequenced Postgres columns, causing
  17-insert-handle.t to fail when run against Postgres.  Reported by
  Eric Schwartz.


0.84  September 4, 2004

ENHANCEMENTS:

- Alzabo::MethodMaker will now warn you when you it creates a method
  that overrides a parent class's method.  This can cause problems
  when you override the table class's name() method with one that
  returns a column object.


BUG FIXES:

- Make Alzabo::Create::Schema->delete work under taint mode.  Reported
  by Dana Hudes.

- Improve Alazbo::PostgreSQL docs, specifically mentioning that if you
  create a Postgres schema with mixed or upper case table names, you
  need to do $schema->set_quote_identifiers(1) for any DML SQL to