SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG

 
 

perl-ORLite-Migrate rpm build for : openSUSE Leap 42. For other distributions click perl-ORLite-Migrate.

Name : perl-ORLite-Migrate
Version : 1.10 Vendor : obs://build_opensuse_org/devel:languages:perl
Release : 1.2 Date : 2017-07-15 07:07:19
Group : Development/Libraries/Perl Source RPM : perl-ORLite-Migrate-1.10-1.2.src.rpm
Size : 0.06 MB
Packager : (none)
Summary : Extremely light weight SQLite-specific schema migration
Description :
the SQLite manpage is a light weight single file SQL database that provides
an excellent platform for embedded storage of structured data.

the ORLite manpage is a light weight single class Object-Relational Mapper
(ORM) system specifically designed for (and limited to only) work with
SQLite.

the ORLite::Migrate manpage is a light weight single class Database Schema
Migration enhancement for the ORLite manpage.

It provides a simple implementation of schema versioning within the SQLite
database using the built-in \'user_version\' pragma (which is set to zero by
default).

When setting up the ORM class, an additional \'timeline\' parameter is
provided, which should be either a monolithic timeline class, or a
directory containing standalone migration scripts.

A *\"timeline\"* is a set of revisioned schema changed, to be applied in
order and representing the evolution of the database schema over time. The
end of the timeline, representing by the highest revision number,
represents the \"current\" anticipated schema for the application.

Because the patch sequence can be calculated from any arbitrary starting
version, by keeping the historical set of changes in your application as
schema patches it is possible for the user of any older application version
to install the most current version of an application and have their
database upgraded smoothly and safely.

The recommended location to store the migration timeline is a shared files
directory, locatable using one of the functions from the File::ShareDir
manpage.

The timeline for your application can be specified in two different forms,
with different advantages and disadvantages.

RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl/openSUSE_Leap_42.3/noarch

Content of RPM  Changelog  Provides Requires

Hmm ... It's impossible ;-) This RPM doesn't exist on any FTP server

Provides :
perl(ORLite::Migrate)
perl(ORLite::Migrate::Patch)
perl(ORLite::Migrate::Timeline)
perl-ORLite-Migrate

Requires :
rpmlib(CompressedFileNames) <= 3.0.4-1
perl(DBD::SQLite) => 1.21
perl(ORLite) => 1.28
perl(File::Path) => 2.04
rpmlib(PayloadIsLzma) <= 4.4.6-1
perl(File::pushd) => 1.00
perl(IPC::Run3) => 0.042
perl(DBI) => 1.58
perl(Params::Util) => 0.37
perl(:MODULE_COMPAT_5.18.2)
perl(File::Which) => 1.07
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
perl(File::Spec) => 3.2701
perl(Probe::Perl) => 0.01


Content of RPM :
/usr/lib/perl5/vendor_perl/5.18.2/ORLite
/usr/lib/perl5/vendor_perl/5.18.2/ORLite/Migrate
/usr/lib/perl5/vendor_perl/5.18.2/ORLite/Migrate.pm
/usr/lib/perl5/vendor_perl/5.18.2/ORLite/Migrate/Patch.pm
/usr/lib/perl5/vendor_perl/5.18.2/ORLite/Migrate/Timeline.pm
/usr/lib/perl5/vendor_perl/5.18.2/x86_64-linux-thread-multi
/usr/share/doc/packages/perl-ORLite-Migrate
/usr/share/doc/packages/perl-ORLite-Migrate/Changes
/usr/share/doc/packages/perl-ORLite-Migrate/LICENSE
/usr/share/doc/packages/perl-ORLite-Migrate/MYMETA.json
/usr/share/doc/packages/perl-ORLite-Migrate/README
/usr/share/man/man3/ORLite::Migrate.3pm.gz
/usr/share/man/man3/ORLite::Migrate::Timeline.3pm.gz

 
ICM