Parents (Total: 4)

The searched file hash is included in 4 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	162732DA2A3D20D619B3920F568315D2
PackageArch	noarch
PackageDescription	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);
PackageMaintainer	https://bugs.opensuse.org
PackageName	perl-Mojo-SQLite
PackageRelease	lp151.2.1
PackageVersion	3.000
SHA-1	0C34E99FA073D337605CB10F35B7A7852087D9EB
SHA-256	05124A6A414027BBDF64CA9FB31377C22ED52F2354C83000ECB8C97E26BEAFCF

Key	Value
MD5	2565F019472C578945990FD2805FAC9F
PackageArch	noarch
PackageDescription	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);
PackageMaintainer	https://bugs.opensuse.org
PackageName	perl-Mojo-SQLite
PackageRelease	lp152.3.2
PackageVersion	3.000
SHA-1	682017710A0E1676F78FB2CD225730F8D561B4D1
SHA-256	FB2EEC0B22F2CF5B4AC38F23BC005462CA5568AFC70E2A6658A49BBF1A6CFA49

Key	Value
MD5	ABA4760A6EB5C9E0F052F157BC507FAA
PackageArch	noarch
PackageDescription	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);
PackageMaintainer	https://bugs.opensuse.org
PackageName	perl-Mojo-SQLite
PackageRelease	lp150.1.3
PackageVersion	3.000
SHA-1	B0F91298FBE08D4BF11A8BF25D6C9CA957C44A40
SHA-256	623A0B317A8CEC20D60F26212E23ECB329DB4994EF16751A05E38D6BBA7E90EC

Key	Value
MD5	AA533FEE618D894D04F124EAA1871DA8
PackageArch	noarch
PackageDescription	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);
PackageMaintainer	https://bugs.opensuse.org
PackageName	perl-Mojo-SQLite
PackageRelease	bp153.1.12
PackageVersion	3.000
SHA-1	948AC24EF84960350362A1C325D6BB16C73CDDB2
SHA-256	B6A36EE5D4C48A40804067038524D9381CF1066698D989F1670A39E2D7271355