| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help |
The search service can find package by either name (apache), provides(webserver), absolute file names (/usr/bin/apache), binaries (gprof) or shared libraries (libXm.so.2) in standard path. It does not support multiple arguments yet...
The System and Arch are optional added filters, for example System could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system.
Mojo::SQLite is a tiny wrapper around DBD::SQLite that makes at https://www.sqlite.org/ a lot of fun to use with the at https://mojolico.us real-time web framework. Use all at http://sqlite.org/lang.html SQLite has to offer, generate CRUD queries from data structures, and manage your database schema with migrations. Database and statement handles are cached automatically, so they can be reused transparently to increase performance. And you can handle connection timeouts gracefully by holding on to them only for short amounts of time. use Mojolicious::Lite; use Mojo::SQLite; helper sqlite => sub { state $sql = Mojo::SQLite->new('sqlite:test.db') }; get '/' => sub { my $c = shift; my $db = $c->sqlite->db; $c->render(json => $db->query('select datetime("now","localtime") as now')->hash); }; app->start; In this example application, we create a 'sqlite' helper to store a Mojo::SQLite object. Our action calls that helper and uses the method Mojo::SQLite/"db" to dequeue a Mojo::SQLite::Database object from the connection pool. Then we use the method Mojo::SQLite::Database/"query" to execute an at http://www.postgresql.org/docs/current/static/sql.html statement, which returns a Mojo::SQLite::Results object. And finally we call the method Mojo::SQLite::Results/"hash" to retrieve the first row as a hash reference. All I/O and queries are performed synchronously. However, the "Write-Ahead Log" journal is enabled for all connections, allowing multiple processes to read and write concurrently to the same database file (but only one can write at a time). You can prevent this mode from being enabled by passing the option 'no_wal', but note that this is incompatible with SQLite databases that have already had WAL mode enabled. See http://sqlite.org/wal.html and DBD::SQLite/"journal_mode" for more information. my $pid = fork || die $!; say $sql->db->query('select datetime("now","localtime") as time')->hash->{time}; exit unless $pid; All cached database handles will be reset automatically if a new process has been forked, this allows multiple processes to share the same Mojo::SQLite object safely. Any database errors will throw an exception as 'RaiseError' is automatically enabled, so use 'eval' or Try::Tiny to catch them. This makes transactions with Mojo::SQLite::Database/"begin" easy. While passing a file path of ':memory:' (or a custom "dsn" with 'mode=memory') will create a temporary database, in-memory databases cannot be shared between connections, so subsequent calls to "db" may return connections to completely different databases. For a temporary database that can be shared between connections and processes, pass a file path of ':temp:' to store the database in a temporary directory (this is the default), or consider constructing a temporary directory yourself with File::Temp if you need to reuse the filename. A temporary directory allows SQLite to create at https://www.sqlite.org/tempfiles.html safely. use File::Spec::Functions 'catfile'; use File::Temp; use Mojo::SQLite; my $tempdir = File::Temp->newdir; # Deleted when object goes out of scope my $tempfile = catfile $tempdir, 'test.db'; my $sql = Mojo::SQLite->new->from_filename($tempfile);
Generated by rpm2html 1.6