Alzabo
view release on metacpan or search on metacpan
install_helpers/pod_merge.pl view on Meta::CPAN
my $to = join '', <TO>;
close FROM or die "Can't close '$file': $!";
close TO or die "Can't close '$t_in': $!";
$to =~ s/\r//g;
$to =~ s/\n
=for\ pod_merge # find this string at the beginning of a line
(?:
\s+
(\w+) # say what POD marker to merge from
)
(?:
\ +
(\w+) # optionally, say what POD marker to merge until (i.e. =head3)
)?
.*? # what we're going to merge (and replace)
\n+
(?=
\n= # next =foo marker, skipping all spaces. This just makes matching stop here
)
/
find_chunk($file, $from, $class, $1, $2)
/gxie;
lib/Alzabo/Intro.pod view on Meta::CPAN
version of Alzabo which created the schema.
Then it will alter the schema as necessary and save it to disk.
This will all happen transparently, as long as the process which
initiated this process can write to the schema files and the directory
they are in.
Alzabo will need the C<Alzabo::Create::*> classes to update the
schema. If these have not been loaded already, Alzabo will do so and
issue a warning to say that this has happened, in case you would like
to restart the process without these classes loaded.
=head1 MULTIPLE COPIES OF THE SAME SCHEMA
It is possible to use the same schema definition with multiple copies
of that schema in the RDBMS. This can be done by setting the
"schema_name" parameter whenever you call a method that connects to
the RDBMS, such as L<<
C<Alzabo::Create::Schema-E<gt>create>|Alzabo::Create::Schema/create >>
or L<<
lib/Alzabo/SQLMaker/MySQL.pm view on Meta::CPAN
=head2 :fulltext
These are functions related to MySQL's fulltext searching
capabilities.
MATCH
AGAINST
IN_BOOLEAN_MODE
NOTE: In MySQL 4.0 and greater, it is possible to say that a search is
in boolean mode in order to change how MySQL handles the argument
given to AGAINST. This will not work with earlier versions.
=head2 :common
These are functions from other groups that are most commonly used.
NOW
COUNT
AVG
( run in 0.775 second using v1.01-cache-2.11-cpan-a1f116cd669 )