[Activeagenda-general] Recent updates

[Mattias T. <mth...@ac...>]

Hi everyone,

This is a heads-up about the latest commits to Active Agenda's SVN
repository (revisions 1022 through 1027).

One thing you might notice when re-generating you AA installation (php
s2a.php -t) is that it will issue a PHP Warning about "multiple primary
keys defined", for the 'cod' and 'mod' modules (Codes and Modules,
respectively). This is because I have changed the primary keys of these
modules, and the warning is issued while the new primary key is being
installed. I didn't implement a way to suppress this warning from being
issued. If you didn't also receive a PHP Error for each of these, then
the change was applied successfully.

Modifying the Codes and Modules modules was necessary in order to
standardize the structure of modules so that all the "global" modules
and functionalities don't have to deal with these two exceptions. Now,
all records in the database can be addressed by a module ID and a
numeric record ID (*).

This opens the way for implementing better import/export functionality,
audit trails, triggers and more!

Cheers,

Mattias

PS: A minor problem that I've just discovered is that the unique key
restriction is not applied to the 'cod' table when the new primary key
is applied. This is applied only the next time the 'cod' module is
re-generated. Until I have found a fix for this (check SVN messages),
please re-generate 'cod' once (just this one time) after all modules
have been successfully generated.

(*) The only exceptions are a handful of "cache" modules, but that is
fine since they only contain data that is only derived from other
modules. Users don't interface with these modules directly either, so
there is no need for screens etc..

-- 
Mattias Thorslund
Active Agenda, Inc.
mth...@ac...
Company: http://www.activeagenda.net
Weblog:  http://activeagenda.net/blog/