view release on metacpan or  search on metacpan

README.pod  view on Meta::CPAN

=back

=head2 Store options into configuration files

FusqlFS leverages L<Getopt::ArgvFile> package to load configuration from files.

Long story short, you can put C<@filename> on command line, it will interpolate
contents of the file into command line. You can place as many @-clauses into
command line as you want. This way you can store some common options into a
file and use it in C<fusqlfs> invocation. For instance, you can place
credentials and database name into F<databaserc> file and then just call
C<fusqlfs @databaserc> to mount it.

As an alternative to @-prefix you can use C<-r> option instead to load
configuration from given file, so you can write C<-r filename> instead
of C<@filename>. This is useful to put into shebang line in fusqlfs config
file:

    #!/usr/bin/fusqlfs -r
    --user=root
    --password=pa$$w0rd

bin/fusqlfs  view on Meta::CPAN

=back

=head2 Store options into configuration files

FusqlFS leverages L<Getopt::ArgvFile> package to load configuration from files.

Long story short, you can put C<@filename> on command line, it will interpolate
contents of the file into command line. You can place as many @-clauses into
command line as you want. This way you can store some common options into a
file and use it in C<fusqlfs> invocation. For instance, you can place
credentials and database name into F<databaserc> file and then just call
C<fusqlfs @databaserc> to mount it.

As an alternative to @-prefix you can use C<-r> option instead to load
configuration from given file, so you can write C<-r filename> instead
of C<@filename>. This is useful to put into shebang line in fusqlfs config
file:

    #!/usr/bin/fusqlfs -r
    --user=root
    --password=pa$$w0rd

lib/FusqlFS/Backend/Base.pm  view on Meta::CPAN

    $self->init();
    return $self;
}

=item connect, disconnect, reconnect

These methods can be used to control database connection in runtime.
Please use them instead of direct DBH object access via $fusqlh->{dbh},
as they make some more work, than simple database {dis,re}connection.

They use credentials, provided on first backend object initialization
with L</new> method above, so no parameters are required.

C<connect> establish new database connection and reinitializes backend.
Backend reinitialization is required, because some backends make some
query preparation, linked to current database connection.

C<disconnect> drops database connection, and C<reconnect> drops database
connection is it's active (checked with L<DBI::ping> method) and
then establish connection anew. This method is used in C<HUP>
signal handler to reset database connection.