NAME

Alzabo::FAQ - Frequently Asked Questions

How can I generate the SQL to turn one schema into another?

Assuming you have schema objects representing these already created (through reverse engineering for example) and both schemas are for the same RDBMS, you can simply do this:

 my @sql = $schema1->rules->schema_diff( old => $schema1, new => $schema2 );

The @sql array will contain all the SQL statements necessary to transform the schema in $schema1 into the schema in $schema2.

If you want to sync a schema object to the current state of the RDBMS backend's schema, check out the Alzabo::Create::Schema->sync_backend method.

How can I make a local copy of the documentation as HTML?

Alzabo comes with a script called make_html_docs.pl. It takes three arguments. The first is the source file directory root. The second is the target directory. The last is the absolute URL path that this target directory represents. If you have perl 5.6.0 or greated installed, it is recommended that you use it to run this script as the Pod::Html module included with more recent Perls does a much better job of making HTML.

If you were in the root of the source directory you might run this as:

 perl ./make_html_docs.pl ./lib /usr/local/apache/htdocs/Alzabo_docs /Alzabo_docs

The script will create an index.html file as well as turning the documentation into HTML.

How can I optimize memory usage under mod_perl?

You should simply preload the Alzabo::Runtime module (which loads all the other modules it needs).

In addition, if you are using Alzabo::MethodMaker, make sure it runs in the parent. This module can create a lot of methods on the fly and each method eats up some memory.

Finally, you can preload one or more schema objects. The easiest way to do this is to simply pass its name to Alzabo::Runtime when you use it, like this:

  use Alzabo::Runtime qw( schema1 schema2 );